portmaster, portupgrade, etc
sgk at troutmask.apl.washington.edu
Fri Oct 6 08:13:44 UTC 2017
On Fri, Oct 06, 2017 at 09:41:28AM +0200, Baptiste Daroussin wrote:
> On Wed, Oct 04, 2017 at 05:15:18PM +0000, Steve Kargl wrote:
> > On Wed, Oct 04, 2017 at 12:16:49PM -0400, Michael W. Lucas wrote:
> > >
> > > Poudriere really needs its own small book. Yes, you can do simple
> > > poudriere installs, but once you start covering it properly the docs
> > > quickly expand. My notes alone are longer than my af3e chapter
> > > limits. (I'll probably publish "FreeBSD Packaging Misery^WMastery" in
> > > 2018).
> > Please include a discussion on how to use poudriere on
> > a system with limited resouces (e.g., 10 GB of free
> > diskspace and less than 1 GB free memory). I know
> > portmaster works well  within an environment with
> > only 4 GB free diskspace and 1 GB memory.
> >  portmaster worked well prior to portmgr's decision
> > to displace simple small tools in favor of a sledge
> > hammer.
> FUD.. portmgr never took any decision like this.
> The problem with portmaster (beside some design flows regarding
> the "not build in a clean room") is that it is not maintained anymore.
> (Note that it has never been maintained by portmgr at all).
I'm well aware of Doug Barton's history with FreeBSD. You
can paint it with whatever color you want.
If you (and other poudriere) contributors stated that flavors/subpackages
would not be supported by poudriere, would flavors/subpackages been
wedged into the ports build infrastructure?
More information about the freebsd-ports