On Tuesday 05 Nov 2013 14:40:46 Bruce Hill wrote: > On Tue, Nov 05, 2013 at 06:15:56AM +0000, Nuno J. Silva (aka njsg) wrote: > > >> On Monday 04 Nov 2013 19:51:32 Alexander Kapshuk wrote: > > >> > On 11/03/2013 02:27 AM, Daniel Campbell wrote: > > >> > > For starters, you should probably merge package.keywords into > > >> > > package.accept_keywords; the latter is the "new" standard name, > > >> > > though Portage will likely support the old names for a while. > > >> > > Just a heads-up on that. > > >> > > > >> > Thanks for a heads-up. I did as you suggested. > > >> > > >> Is there going to be a portage news article on this, or did I miss it? > > > > > > It wasn't two or three years ago... > > > > > > mingdao@server ~ $ eselect news read 5 > > > 2012-09-09-make.conf-and-make.profile-move > > > > > > Title make.conf and make.profile move > > > Author Jorge Manuel B. S. Vicetto > > > <[email protected]> Posted 2012-09-09 > > > Revision 1 > > > > > > Starting next week, new stages will have make.conf and make.profile > > > moved from /etc to /etc/portage. This is a change in the installation > > > defaults, that will only affect new installs so it doesn't affect > > > current systems. > > > > > > Current users don't need to do anything. But if you want to follow the > > > preferred location, you may want to take the chance to move the files > > > in your system(s) to the new location. > > > > But that's about make.conf, not about package.keywords. > > mingdao blushes
Actually it was in a portage news article, but not an article about portage or /etc/portage/package.* changing its naming convention. It was mentioned in passing in the latest news article about python-exec. I carry on regardless, perhaps foolishly, on the assumption that when stable portage changes its configuration file structure someone will let us know. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
