Am Mittwoch, 12. Januar 2022, 11:49:26 CET schrieb David Edmundson: > > This triggered yet another idea with me, and I came across > > https://www.freedesktop.org/software/systemd/man/environment.d.html > > upon which I tried to add a file > > /home/mydevuser/.config/environment.d/60-test.conf > > with the content > > --- 8< --- > > XDG_DATA_DIRS=/home/mydevuser/my/share::${XDG_DATA_DIRS:-/usr/local/share/ > > :/ usr/share/} > > --- 8< --- > > logged into a new session et voilĂ , the session D-Bus now sees my D-Bus > > service files and starts the services as expected. > > The equivalent for non-systemd people is to setup `pam_env` with user > env turned on to do the same thing at roughly the same time.
Okay, will read up on that more. > The drawback is you're always affecting that user, it's not on a per > login basis, which works for you, but not everyone. Yes, there seem to be multiple workflows/use-cases, so there seems to be need for multiple solutions. The one I am looking at here is when working on single apps/services, in the usual fashion when using kdesrc-build which also modifies the user's .bashrc/.zshrc file for persistent addition of the local installed software, This is where I look for the counterpart to ensure also D-Bus service files will be seen, so would be fine with a similar grave change of user settings. Not yet looked further, only later today/this week, but guess I/we should look more at that for this use case? Cheers Friedrich