The ports collection has some serious issues
Werner.Griessl at uni-bayreuth.de
Thu Dec 8 13:48:06 UTC 2016
On 12/08/16 13:16, RW via freebsd-ports wrote:
> 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.
> freebsd-ports at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
I use portsnap in combination with portupgrade
Werner Grießl D-95440 Bayreuth, Germany
Universitaet Bayreuth Tel.: +49 921 55 2685
IT-Servicezentrum/Netze NW2 3.2.U1.143
More information about the freebsd-ports