Re: FreeBSD ports community is broken [port building configuration notes]

From: Jamie Landeg-Jones <jamie_at_catflap.org>
Date: Tue, 20 Feb 2024 14:42:00 UTC
"Edward Sanford Sutton, III" <mirror176@hotmail.com> wrote:

> > What's the reasoning behind people claiming a shift from "make install"
> > to poudriere is necessary?
>
>    I don't consider it necessary, but building in a clean environment is 
> desirable to minimize issues and maximize uptime. Some ports will fail 
> to build or install when certain other packages have been installed; 
> proper solution is to open a PR to get such cases identified and 
> resolved. I'd go as far as to say a port should be marked as 
> incompatible with itself if it uses already installed tools from an 
> older version of the port or from a non-dependent package in place of 
> ones that were built in the port's work directory as I have had builds 
> fail doing an x86-x64 rebuild+reinstall step without first removing them 

Thanks for the very detailed reply. I won't quote it all, but it was
all relevant and useful.

And I agree - I definitely think that a port has to pass a completely clean
install before being committed.

From the user side, I also upgrade all ports at once some of the time, due
to the issues you mention, and yes, it is a pain in the arse to do partial
upgrades.

Basically, I either agreed, or now agree, with everything you wrote.

I think I was reading into this thread that the ports system as we know it
was being deprecated in favour of poudriere.

Yes, making the ports system more resilient is something I'd love to get
involved with, but as long as the current system doesn't get exceptionally
worse, I'm fine with it!

Thanks again, Jamie.