I did some research on this. See
https://help.ubuntu.com/community/EnvironmentVariables
There are several places that we could use to specify $PATH:
===Session-wide environment variables===
~/.profile - This is probably the best file for placing environment
variable assignments in, since it gets executed automatically by the
DisplayManager during the startup process desktop session as well as by the
login shell when one logs-in from the textual console.
~/.bash_profile or ~./bash_login - If one of these file exist, bash
executes it rather then "~/.profile" when it is started as a login shell. (Bash
will prefer "~/.bash_profile" to "~/.bash_login"). However, these files won't
influence a graphical session by default.
~/.bashrc - Because of the way Ubuntu currently sets up the various script
files by default, this may be the easiest place to set variables in. The
default configuration nearly guarantees that this file will be executed in each
and every invocation of bash as well as while logging in to the graphical
environment. However, performance-wise this may not be the best thing to do
since it will cause values to be unnecessarily set many times.
===System-wide environment variables===
/etc/environment - This file is specifically meant for system-wide
environment variable settings. It is not a script file, but rather consists of
assignment expressions, one per line. Specifically, this file stores the
system-wide locale and path settings.
/etc/profile - This file gets executed whenever a bash login shell is
entered (e.g. when logging in from the console or over ssh), as well as by the
DisplayManager when the desktop session loads. This is probably the file you
will get referred to when asking veteran UNIX system administrators about
environment variables. In Ubuntu, however, this file does little more then
invoke the /etc/bash.bashrc file.
/etc/bash.bashrc - This is the system-wide version of the ~/.bashrc file.
Ubuntu is configured by default to execute this file whenever a user enters a
shell or the desktop environment.
Obviously, we shouldn't use the per-user ones because there might be
several users on a system. Also, some of these files might already be
owned by a package (most are shipped by bash itself). /etc/environment
looks like the best option since it is system wide and not owned. Maybe
we could ship a custom version of that?
--
You received this bug notification because you are a member of Team UGR,
which is subscribed to ugr-meta.
https://bugs.launchpad.net/bugs/778900
Title:
Cannot start games, wrong $PATH
Status in Ubuntu Gnome Remix Metapackages:
Confirmed
Bug description:
can't start foobillard or any other game that is located in /usr/games
,from the menu or from any location Inside a terminal because
/usr/games isnt't in the Environment Variable Path.
--
Mailing list: https://launchpad.net/~ubuntugnometeam
Post to : [email protected]
Unsubscribe : https://launchpad.net/~ubuntugnometeam
More help : https://help.launchpad.net/ListHelp
