On Wednesday, April 21, 2021 at 10:20:37 PM UTC-7 Cameron D wrote: > Would the simplest option be to make more effort to discourage setup.py > installs with a few warnings? > > Think no. It's already discouraged. The problem is that the users ignore the docs saying 'you need some skills to install this way'.
> On the deb package installs there are wee_xxx wrapper scripts placed in > /usr/bin so the added PATH complexity is not needed. > > That's a little contrary to the idea of setup.py putting everything weewx-related into /home/weewx other than the startup file hook of course. > If they rely on sudo, then I don't think it sources those extra >>> /etc/profile.d files. >>> >> >> It's already sourced in in the non-privileged shell you ran sudo from, so >> that's not an issue. Tested on multiple variants of linux. >> >> > Debian 10 removed that security hole with the default *securepath* > setting. > > Sigh. Yes. I updated my debian10 vagrant box and retested. When I did 'sudo bash' the appended path indeed disappeared for root. We'd need to append /home/weewx/bin to root's $PATH too. Not as sure I like that concept. This points to how hard this stuff is to do portably enough. Still hoping somebody comes up with a simple solution here. We get soooooooo many problem reports that all center around the same things. Users trying to do privileged things without using sudo (permissions issues) and users who don't set their $PATH up correctly. We can't make them read the docs, learn the docs, or follow the docs. That's for sure. Hoping there's a technical solution. -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/0476d5e6-2a18-472b-ab20-cb19b7d7a18an%40googlegroups.com.
