Re: packages mucking in /usr/local/?
Colin Watson <cjwatson@debian.org> writes:
> On Sun, Aug 24, 2003 at 05:35:41AM +0800, Dan Jacobson wrote:
>> Gentlemen, do
>> $ find /usr/local -mtime -222
>> /usr/local/lib/libxbase-2.0.so.0
>> /usr/local/lib/libxbase.so
>
> If those came from a package, they're bugs.
>
>> /usr/local/lib/python2.2/site-packages
>> /usr/local/lib/python2.3/site-packages
>> /usr/local/lib/texmf/ls-R
>> /usr/local/share/emacs/21.3
>> /usr/local/share/emacs/21.3/site-lisp
>> /usr/local/share/octave/site-m...
>
> Those aren't bugs (well, possibly apart from the TeX one, dunno about
> that).
Same idea as described below (tex is slightly different, its packaging
system likes to have an index file).
> 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 directories 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.
>
--
A.J. Rossini
rossini@u.washington.edu http://www.analytics.washington.edu/
Biomedical and Health Informatics University of Washington
Biostatistics, SCHARP/HVTN Fred Hutchinson Cancer Research Center
UW : FAX=206-543-3461 | moving soon to a permanent office
FHCRC: 206-667-7025 FAX=206-667-4812 | Voicemail is pretty sketchy/use Email
CONFIDENTIALITY NOTICE: This e-mail message and any attachments may be
confidential and privileged. If you received this message in error,
please destroy it and notify the sender. Thank you.
Reply to: