Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 293898 - dispatch-conf Needs to Support ROOT Environment Variable
Summary: dispatch-conf Needs to Support ROOT Environment Variable
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Tools (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 859439
  Show dependency tree
 
Reported: 2009-11-20 21:33 UTC by Ben
Modified: 2022-09-25 07:56 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ben 2009-11-20 21:33:19 UTC
Emerge supports the ROOT environment variable.  ROOT enables emerge to target a separate Gentoo file system for updates, etc.  When one uses emerge with ROOT set to something other than "/" and emerge places new config files in ${ROOT}/etc/init.d, the dispatch-conf script is unable to process the new config files.  The dispatch-conf script handles files only in /etc/init.d -- not ${ROOT}/etc/init.d.

The etc-update script properly pays attention to the ROOT environment variable, and processes new config files in ${ROOT}/etc/init.d.

The dispatch-conf script should pay attention to the ROOT environmental variable just as the etc-update script does.
Comment 1 Leho Kraav (:macmaN @lkraav) 2011-12-24 20:16:30 UTC
ran into this today and am wondering is this on anyone's radar that's capable of doing this enhancement? or some qualified assessment on how low this fruit is hanging?
Comment 2 Zac Medico gentoo-dev 2011-12-24 20:31:27 UTC
In portage-2.1.10.41 and later there's a PORTAGE_OVERRIDE_EPREFIX variable that will give dispatch-conf the behavior that you want. However, this variable is experimental and support for it is subject to change.