On Wed, Nov 22, 2017 at 9:23 PM, Chris H wrote:
> On Wed, 22 Nov 2017 21:12:28 -0800 "bob prohaska"
> said
>
> On Wed, Nov 22, 2017 at 08:32:53PM -0800, Kevin Oberman wrote:
>> > > Stale ports SHOULD not be an issue. Normally old ports are updated
>> > automatically. It is important that your po
Can I have someone take a look at this port bug report:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223565
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd
On Thu, Nov 23, 2017 at 12:51:56AM -0800, Yuri wrote:
> On 11/22/17 08:59, Brooks Davis wrote:
> > Looking to the future, is the port an obviously candidate for FLAVORS or
> > multi-packages? If so, they you probably want to keep the current
> > plist. If not, then I guess it depends on your conf
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
On 11/22/17 08:59, Brooks Davis wrote:
Looking to the future, is the port an obviously candidate for FLAVORS or
multi-packages? If so, they you probably want to keep the current
plist. If not, then I guess it depends on your confidence that the port
will remain well behaved.
Flavors and mult
