The ports collection has some serious issues

RW rwmaillists at
Thu Dec 8 12:16:33 UTC 2016

On Thu, 8 Dec 2016 05:16:24 +0000
Daniil Berendeev wrote:

> 1) portmaster is not nice for the user.
> If it comes over an error even in one little tiny port that is a
> dependency for something bigger , it will abort its work and leave all
> the other ports not updated. So, if you try to to do `portmaster -af`,
> you should not forget `-m DISABLE_VULNERABILITIES=yes` (we will return
> to this one later) and you must pray to God for not coming around a
> circular dependency or some port that would fail to deinstall its
> older version. You can't leave portmaster for a night to update all
> the needed ports and deal with broken ones in the morning, you need
> to cherry pick the broken ports and ignore them, and then try to deal
> with them.
> Although portmaster is not releated to the FreeBSD project and is an
> outside tool, there aren't any alternatives from the project itself.
> So use it or die. Not a nice situation.

There's portupgrade. It doesn't stop on the first error but carries on
with ports that don't depend on any broken ports. 

More information about the freebsd-ports mailing list