Re: Our build system may be broken: /bin vs /usr/bin
Russ Allbery writes ("Re: Our build system may be broken: /bin vs /usr/bin"):
> Marco d'Itri <md@Linux.IT> writes:
> > Actually this is the root problem: policy says that packages should use
> > the $PATH to search for commands, but your package (like many others)
> > hardcodes their full path.
> Policy only says that for maintainer scripts. I agree that it's not a
> good idea in any location, but I don't believe we've explicitly forbidden
> it anywhere.
We don't even have consensus that it is a bug! We have, for example,
at least one important component which *requires* hardcoded paths in
their critical configuration files.
Ian Jackson <firstname.lastname@example.org> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.