Date: Tue, 30 May 2017 16:38:34 -0400 From: Jim Ohlstein <jim@mailman-hosting.com> To: Adam Weinberger <adamw@adamw.org>, Thomas Mueller <mueller6722@twc.com> Cc: freebsd-ports@freebsd.org Subject: Re: The future of portmaster Message-ID: <1496176714.1095.44.camel@mailman-hosting.com> In-Reply-To: <9284B642-95B4-459E-859E-DAA9C665954B@adamw.org> References: <201705301351.v4UDpHwY048949@mech-as222.men.bris.ac.uk> <9FEDBFCE-27D1-432B-926B-7BF401AD7B19@adamw.org> <B7.5D.01815.EC3DD295@dnvrco-omsmta03> <9284B642-95B4-459E-859E-DAA9C665954B@adamw.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2017-05-30 at 14:25 -0600, Adam Weinberger wrote: > > On 30 May, 2017, at 14:19, Thomas Mueller <mueller6722@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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1496176714.1095.44.camel>