Matthias Urlichs <matth...@urlichs.de> writes: > On 07.05.25 12:00, Santiago Vila wrote: >> For example, some configure script might look in >> the PATH and decide that sh is in /usr/bin and ship shell scripts >> as #!/usr/bin/sh. > > That's not a problem, because today's default (according to my > /etc/login.defs) is "/usr/local/bin:/usr/bin:/bin" (plus /sbin for > root, plus …/games for non-root), i.e. with the symlinks last.
One problem is that there is no policy on what PATH can or should be when building a Debian package, or is there? So if some package build system (like mine) uses 'setpriv' to drop privileges they will get /bin before /usr/bin, and in this situation Santiago's concerns apply. I think a reasonable conservative system policy is PATH=/usr/bin and anything beyond that is something the user or system administrator have to add. I think we should give up on /usr/games and move those executables to /usr/bin, renaming any binaries that conflict. /Simon
signature.asc
Description: PGP signature
