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

On Sun, 18 Feb 2024 08:52:55 -0800
Mark Millard <marklmi@yahoo.com> wrote:

> > It should not require
> > prodiere running on a supermassive machine to work (in many cases
> > portmaster and make install recursion fail where prodiere works).  
> 
> As for configuring for small, slow systems relative to
> resource use, I provide some settings that I've
> historically used below. Then I have some other notes
> after that material.


I wrote about the fact that it is bad to demand a poudriere and use
its absence as an argument.

From my point of view, Poudriere is a tool that FreeBSD Foundation wrote
for themselves and those who want to assemble the entire port of ports.

 
> As far as more ports building in poudriere than in
> "portmaster and make install recursion" in other
> respects than resources: it is easier to make ports
> build in poudriere. It provides the simpler/cleaner
> context for the individual builders. More things
> lead to failure outside poudriere that are just not
> issues when poudriere is used so more care is needed
> setting up the ports for the likes of portmaster use.
> (And, yes, I used to use portmaster.) The required
> range of testing contexts is wider for use of the
> likes of portmaster to know that the port build will
> just work in the full range of contexts.
> 
> Such issues adds to the port maintainer/committer
> development burdens when portmaster or the like are
> the target level/type of support.
 

This topic is not about the assembly of ports, it is about
problems in the community of people.

Poudriere is useless when for 1.5 months they cannot correct
the work of a key dependence.
Poudriere is useless when the functionality you need is not
accepted simply because one person wished.