On Thu, Apr 7, 2016 at 10:54 PM, Jamie Zawinski <j...@jwz.org> wrote: > Having xscreensaver override and ignore the $PATH that the user passed in is > a terrible idea.
Since we are in control of where we install the hacks (/usr/lib/xscreensaver), it is not that bad. But it would prevent the user from adding his own hacks somewhere random and have them launched just by setting the $PATH. Unless he patches and rebuilds xscreensaver himself :) Is it not possible to specify the full path in the app-default file? That would address above user case. Or is there other user cases I am missing? We do have the problem that there are name clashes. How can we handle this if we do not ignore (alt. parts of) the $PATH? We wouldn't like to add a namespace to all the hack binaries to avoid name clashes. And I don't think it is realistic that the xscreensaver package takes monopoly on names like "zoom". Tormod > > But if init scripts are involved, perhaps those scripts should launch > xscreensaver without /usr/games/ on $PATH. > > -- > Jamie Zawinski https://www.jwz.org/ https://www.dnalounge.com/
