ons 2011-05-25 klockan 19:14 +0100 skrev Matthew Garrett:
> If they're in their path, other utilities are going to misbehave in
> ways
> that will be difficult to debug.
The user could add the directory to PATH without exporting PATH to
subprocesses, or they could use the shell's alias functionality instead.
Then it will only be used when they type the command name in their own
shell.
Actually, the user must make sure to do this after /etc/profile.d/* is
sourced since those might break.
I don't know in what way 9base is useful but I think the relevant
questions here are:
Would it be ok for a package to
1. Install a number of prefixed binaries in /usr/bin/
2. Install a number of unprefixed binaries
in /usr/lib/<pkgname>/bin/
3. Install some files in /usr/share/<pkgname>/profile.d/ (or
something) which are meant to be sourced in the user's shell
?
Is /usr/lib/<pkgname>/bin ok for both arch in multilib? Or does it have
to be /usr/lib64 on x86_64 for some reason?
Btw, using shell aliases means that it won't even need to install
anything in /usr/lib/*/bin.
If something can be packaged in a way that will not break things even if
the package is installed and won't increase the size of a minimal
install through dependency creep then let them. :)
/abo
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
