The ports collection has some serious issues

Warren Block wblock at
Thu Dec 15 16:29:29 UTC 2016

On Thu, 15 Dec 2016, RW via freebsd-ports wrote:

> On Thu, 15 Dec 2016 07:40:46 -0700 (MST)
> Warren Block wrote:
>> On Thu, 8 Dec 2016, Matt Smith wrote:
>>> On Dec 08 05:16, Daniil Berendeev wrote:
>>>> 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.
>>> People have been trying to get portmaster deprecated and removed
>>> from the handbook but have met with resistance.
>> Well, yes.  Because it works, has no dependencies, and there is no
>> equivalent replacement.  Except maybe portupgrade, which has legacy
>> problems like poor default options.
> That's a very minor issue, and an absurd excuse to rule-out portupgrade.

I didn't rule it out.  Portupgrade gets some of the defaults wrong, like 
not running all the 'make config' steps first.  That's a legacy issue 
because if the default changes, it could conceivably cause problems for 
existing users.  Beyond that, other than a dependency on Ruby, 
portupgrade at least exists in the same space as portmaster.

More information about the freebsd-ports mailing list