On Sat, Jan 29, 2005 at 05:40:05PM +0100, Santiago Vila wrote: > So I'll repeat: Please read the logs for non-bug Bug#292759, where the > author explains the rationale for putting gettext.sh in /usr/bin.
you want ". gettext.sh" to work, which means you want it somewhere
in the default system path. you don't want to hard-code the
paths, which makes sense. however, it is shell scripts that are
to do this, not users, so why not do something like this in
any script that uses gettext:
#!/bin/sh
PATH=${PATH}:/usr/share/gettext/scripts
. gettext.sh
that way, you don't pollute /usr/bin with non-executables (which i would
argue does break policy/fhs in the sense that at least it's non
executable), you don't have to hard code the path, and the user can
override it by placing another gettext.sh in their path.
alternately, you could hard code it, but test for a user-environment
variable that could override the default location (though i think
the previous suggestion is less hackish).
sean
--
signature.asc
Description: Digital signature
