The future of portmaster

[Jim Ohlstein]

On Tue, 2017-05-30 at 14:25 -0600, Adam Weinberger wrote:
> > On 30 May, 2017, at 14:19, Thomas Mueller <mueller6722 at twc.com>
> > wrote:
> > 
> > 
> > One thing I forgot to mention in my last post is that the UPDATING
> > file looks geared to portmaster and portupgrade.
> > 
> > Users are thus led to believe that portupgrade and portmaster are
> > still the currently recommended tools.
> > 
> > If the ports people want to get users to switch to synth or
> > poudriere, updating instructions should include synth and
> > poudriere.
> 
> There are no updating instructions for them. They do the right thing
> automatically. Only portmaster needs its hand held every time
> something gets updated.
> 
> The only difference is that things go into a make.conf in
> /usr/local/etc/poudriere.d/ rather than /etc/make.conf (see
> CUSTOMISATION in poudriere(8) for details), and I don't know if synth
> has a special place for it too.
> 

And not only that, but poudriere reads MOVED as well.

> 
-- 
Jim Ohlstein
Professional Mailman Hosting
https://mailman-hosting.com/