Summary: | Add ~/bin to PATH | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Luke-Jr <luke-jr+gentoobugs> |
Component: | [OLD] Core system | Assignee: | Martin Schlemmer (RETIRED) <azarah> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | mr_bones_, releng |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Luke-Jr
2003-09-01 14:29:57 UTC
The administrator can already alter /etc/env.d/00basic and run env-update if they want merely to add ~/bin to $PATH. Unfortunately /etc/profile, prefixes /bin and /usr/bin to the PATH value set in /etc/profile.env rather than append, so it's unlikely that a user will gain the benefit they hope for (it would be useful for example to select distcc usage or ccache, without extending paths by using a script in /usr/local/bin or ~/bin). A more convenient solution for site specific customisation, would be to check for existance of an /etc/profile.local scripts, at end of profile, so customisations can be maintained seperately from the ebuild's. Then the PATH ordering can easily be over-ridden by the administrator, and $HOME/bin can be added to $PATH only if it exists. Even better would be to extend the /etc/env.d/ to support a site directory, so the same env-update processing which produces profile.env for bash and csh shells, could be re-used for local customisations. or the user can add to .bash_profile: -- export PATH="~/bin:$PATH" -- The user could add the entire PATH in their profile, too. ~/bin should be a default. |