Here's the relevant section of the Debian Policy Guide
http://www.debian.org/doc/debian-policy/ch-opersys.html
9.1.2 Site-specific programs
As mandated by the FHS, packages must not place any files in /usr/local,
either by putting them in the file system archive to be unpacked by dpkg
or by manipulating them in their maintainer scripts.
However, the package may create empty directories below /usr/local so
that the system administrator knows where to place site-specific files.
These are not directories in /usr/local, but are children of directories
in /usr/local. These directories (/usr/local/*/dir/) should be removed
on package removal if they are empty.
Note, that this applies only to directories below /usr/local, not in
/usr/local. Packages must not create sub-directories in the directory
/usr/local itself, except those listed in FHS, section 4.5. However, you
may create directories below them as you wish. You must not remove any
of the directories listed in 4.5, even if you created them.
Since /usr/local can be mounted read-only from a remote server, these
directories must be created and removed by the postinst and prerm
maintainer scripts and not be included in the .deb archive. These
scripts must not fail if either of these operations fail.
For example, the emacsen-common package could contain something like
if [ ! -e /usr/local/share/emacs ]
then
if mkdir /usr/local/share/emacs 2>/dev/null
then
chown root:staff /usr/local/share/emacs
chmod 2775 /usr/local/share/emacs
fi
fi
in its postinst script, and
rmdir /usr/local/share/emacs/site-lisp 2>/dev/null || true
rmdir /usr/local/share/emacs 2>/dev/null || true
in the prerm script. (Note that this form is used to ensure that if the
script is interrupted, the directory /usr/local/share/emacs will still
be removed.)
If you do create a directory in /usr/local for local additions to a
package, you should ensure that settings in /usr/local take precedence
over the equivalents in /usr.
However, because /usr/local and its contents are for exclusive use of
the local administrator, a package must not rely on the presence or
absence of files or directories in /usr/local for normal operation.
The /usr/local directory itself and all the subdirectories created by
the package should (by default) have permissions 2775 (group-writable
and set-group-id) and be owned by root.staff.
--
rubygems bin in PATH potentially breaks other applications and violates all
sense of decency in packaging.
https://bugs.launchpad.net/bugs/262063
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
