Hi,
On Thu, 8 May 2008, James Stroud wrote:
On May 7, 2008, at 3:07 PM, Chris Waddling wrote:
so even temporarily putting a library where it doesn't belong
Actually, this is what /usr/lib is for (except for the "doesn't" part).
According to the Filesystem Hierarchy Standard 4.7 regarding the general
requirements and limitations of files placed in /usr/lib: "/usr/lib includes
object files, libraries, and internal binaries that are not intended to be
executed directly by users or shell scripts."
If it fulfills the definition and is not expressly forbidden, then its
reasonable to assume its allowed.
The issue here is not _what_ certain directories contain, but _how_ the
contents of those directories are maintained, and the FHS has nothing to say
about that. In most distributions, /usr/lib will be one of the directories
maintained by the system's software packaging mechanism (zypper, rug, dpkg, or
whatever). You would be well advised not to put files willy-nilly into it. I
can expand on this if anyone who doesn't already know is interested.
Whenever someone finds themselves wanting to put a file in a directory like
/usr/bin, /usr/lib, /sbin etc., there will almost always be a better way, as
indeed this thread has shown.
Regards,
Peter.
