[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: packages mucking in /usr/local/?



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).

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.

-- 
Colin Watson                                  [cjwatson@flatline.org.uk]



Reply to: