Re: shell script sniplets in /usr/bin?
Santiago Vila <sanvila@unex.es> writes:
> On Sun, 30 Jan 2005, sean finney wrote:
>
>> think about the purpose path is supposed to serve. the bash man page
>> says PATH is "The search path for commands". it mentions nothing of
>> shell scripts to be included/sourced.
>
> This is from bash(1):
>
> . filename [arguments]
> source filename [arguments]
>
> Read and execute commands from filename in the current shell
> environment and return the exit status of the last command executed
> from filename. If filename does not contain a slash, filenames in
> PATH are used to find the directory containing filename. The file
> searched for in PATH need not be executable.
>
>
> --
> To UNSUBSCRIBE, email to debian-policy-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Another little thing on this: MULTIARCH
Post sarge gettext base will have to be split into common data,
architexture dependend libs and binaries:
Package: gettext-base
Architecture: any
Multiarch: no
Depends: gettext-base-common (= 1.2.3), gettext-base-libs (>= 1.2.3)
Description: GNU Internationalization utilities for the base system
Paclage: gettext-base-common
Architecture: all
Description: GNU Internationalization shared files for the base system
Package: gettext-base-libs
Architecture: any
Multiarch: yes
Description: GNU Internationalization shared libs for the base system
Where do you want to put gettext.sh? Once in every gettext-base or
only once in gettext-base-common?
MfG
Goswin
Reply to: