The ports collection has some serious issues
peter at rulingia.com
Fri Dec 16 05:42:20 UTC 2016
On 2016-Dec-15 19:31:22 +0100, list-freebsd-ports at jyborn.se wrote:
>On Thu, Dec 15, 2016 at 01:18:05PM -0500, George Mitchell wrote:
>> On 12/15/16 09:40, 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. [...]
>> Warren, you have hit the nail on the head. -- George
>I never have problems with portmaster.
I don't know about never - I think I managed to get it into a dependency
loop once - but I've never had any issues that I could not resolve or
that would entice me to look at an alternative.
>(But portupgrade could at times be an utter mess,
>I never looked back after switching to portmaster
>many years ago.)
Likewise, portupgrade would explode and shower my system with bits of
corrupt database to often for comfort. At least part of that was caused
by portupgrade depending on quite a few other ports and getting confused
when it updated things whilst it was using them.
>And I'm not at all interested in running poudriere
>or synth, thank you.
Interestingly, the most vocal proponent of deleting portmaster and
portupgrade is the author/maintainer of synch.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 949 bytes
Desc: not available
More information about the freebsd-ports