On Sun, Sep 24, 2023 at 15:55 Michael Kjörling <2695bd53d...@ewoof.net> wrote:
> On 24 Sep 2023 15:45 -0500, from tom.brow...@gmail.com (Tom Browder): > > Bummer, unfortunately, that's the answer I expected. Now if I can find a > > clean way to do that consistently. > > Well, I still think the gist of my suggestion stands: make a script to > set up $PATH the way you want it (for both root and non-root users > respectively); put that script somewhere, anywhere really; and invoke > it from where you need $PATH set up. > > That way, if you miss some path (no pun intended), all you need is to > figure out how to execute or source a script through there in such a > way that it affects the resultant environment; and if you want to make > adjustments later, you can do that in _one_ location. In effect, I will doing that. I'm in the process of automating non-package installation of Raku on modern Debian hosts. That was the genesis of my question, and I will be inserting the required PATH info at the approriate place for any login type as pointed out by Greg and the Debian docs. Thanks, Michael and Greg. -Tom
