|Summary:||Please update handbook(s) to recommend /etc/portage/profile/package.use|
|Product:||[OLD] Docs on www.gentoo.org||Reporter:||David J Cozatt <djcozatt>|
|Component:||Installation Handbook||Assignee:||Docs Team <docs-team>|
|Package list:||Runtime testing required:||---|
Description David J Cozatt 2011-01-09 04:18:25 UTC
The current docs recommend using /etc/portage/package.use Host specific should be in /etc/portage/profile tuxmobl david # man portage | grep site-specific site-specific overrides go in /etc/portage/profile/ site-specific overrides of /etc/make.profile/ Specifies site-specific repository configuration informa- are inherently not site-specific. WARNING: Use of Reproducible: Always
Comment 1 Mike Gilbert 2011-01-09 04:29:40 UTC
The portage(7) man page lists both /etc/portage/package.use and /etc/portage/profile/package.use as valid locations to set package-specific use flags. /etc/portage/profile/* is there to allow overriding of profile-level settings. In the case of package.use, both files accomplish essentially the same thing.
Comment 2 nm (RETIRED) 2011-01-09 08:54:24 UTC
/etc/portage/package.use is fine; the Portage team hasn't announced it's being deprecated or anything. The handbooks will stay as-is.
Comment 3 David J Cozatt 2011-01-09 23:58:35 UTC
I would agree except that...when updating baselayout /etc/portage/package.use was erased. I didn't have it config protected the first time I did this...and portage will soon go to baselayout 2 It's a minor point though I suppose; since usually baselyout updates don't seem to do this. Summing, I believe anyone who uses the file as directed in the handbook would risk having the file erased when updating to baselayout 2 and all their custom configuration. If they used /etc/portage/profile this would not be the case.
Comment 4 Mike Gilbert 2011-01-10 00:15:53 UTC
That sounds like an issue with CONFIG_PROTECT_MASK or with the baselayout ebuild, not with handbook documentation.