freebsd-ports Digest, Vol 619, Issue 2

Konstantinos Koukopoulos koukopoulos at
Tue Mar 31 14:23:17 UTC 2015

On 31/03/2015 15:00, "Chris H" <bsd-lists at> wrote:
> Since you are the maintainer, the answer is ultimately your choice. But
> your answers to the above questions will largely determine the ultimate
> value of your port. 
> You needn't open a pr(1). [personally] I would wait to see if the
> problem actually manifests itself in "real life".
> poudriere is one option. But there is no good reason you can't create
> a jail, use a VM, or use any other means to create a suitable
> environment as a test bed, to isolate the problem/issue. Lastly; If you
> truly believe the problem exists in the source, you should report it
> upstream. Unless you want to fix it for them. 
> P.S. don't forget that you can always mark the port broken for
> ARCH, or OSVERSION, or any combination of the two.

thanks for your advice. I'll try and reproduce the failure, time permitting.

More information about the freebsd-ports mailing list