Re: shell script sniplets in /usr/bin?
- To: debian-policy@lists.debian.org
- Subject: Re: shell script sniplets in /usr/bin?
- From: Eduard Bloch <edi@gmx.de>
- Date: Sun, 30 Jan 2005 15:10:17 +0100
- Message-id: <20050130141017.GA10916@zombie.inka.de>
- In-reply-to: <Pine.LNX.4.62.0501301413290.22419@cantor.unex.es>
- References: <20050129161830.GA5002@seehuhn.de> <87u0p0422b.fsf@toncho.dhh.gt.org> <20050129171721.GA17568@seehuhn.de> <87hdl03z8b.fsf@toncho.dhh.gt.org> <20050130121827.GA5638@seehuhn.de> <Pine.LNX.4.62.0501301413290.22419@cantor.unex.es>
#include <hallo.h>
* Santiago Vila [Sun, Jan 30 2005, 02:28:01PM]:
> Where does dlsym() look up the libraries? In /usr/lib. So Debian
> installs C libraries in /usr/lib/. Fine.
That's wrong. Packages should avoid the installation of non-versioned
(no SONAME) libraries in /usr/lib. Such plugins can often be loaded from
special locations after minor changes in the program source. This is
also often allowed and supported by upstream's configuration system.
> Where does "." look up the libraries? Anywhere in $PATH. In particular in
> /usr/bin.
>
> If the Debian project designates a particular directory for shell script
> function libraries, and puts this directory in $PATH by default, GNU gettext
> will happily install its contents there.
Crap thinking. AFAICS no one of hundreds of maintainers came to the idea
to put shell snippets there.
ls /usr/bin/ -la | grep -v rwx | grep -v rws
So why is your case different?
> So, the common sense says /usr/bin is ok for gettext.sh, not the opposite.
Common sense is something shareable with many other people. He presents
only _his_ point of view.
Regards,
Eduard.
--
<azeem> schreibs meinetwegen in die fortunes :P
Reply to: