Greg’s note conveys what I was trying to say about system applications better than I could. The truth is, if Weewx decides to go the “stuff in installing user’s home directory” route - I’ll just make it installed by the Weewx user, which gets much (not all) of what I want. I do believe that the normal Python installers are optimized for a use case that isn’t Weewx, or any , and programs like ufw and fail2ban that are - as Greg points out - single instance system installs vs something any user can run. They are going to struggle to fit into the python install shoehorn even more than Weewx, which doesn’t require root access to run, like these two do.
Sent from my iPhone > On Nov 8, 2022, at 3:36 PM, Greg Troxel <g...@lexort.com> wrote: > > > Tom Keffer <tkef...@gmail.com> writes: > >> Greg: The package installers would continue to install to /etc/weewx. For >> those who want something that "just works" that continues to be a good >> idea. However, there is a disadvantage: it requires sudo to install and >> edit. Many of us also prefer to have everything under one subdirectory >> (such as /home/weewx or ~/.weewx, or what have you). > > Sure, I realize some people prefer a root for all of weewx, and some > want it to be like one of the other 200 python programs. > >> While many apps install to $prefix/etc, not all do. Many depend on >> configuration settings under ~/.local or their own subdirectory. It's by no >> means universal. > > Agreed, but I think there is a difference in semantics. Some things > are programs that are installed in the system and configured, as a > single instance, systemwide. I see weewx in the normal case as like > that, similar to nginx, sshd, pgsql, and many others. > > Things that look in the user's homedir I see more like gimp, where the > program is installed so that it is available, but there is no singleton > system instance of it. Each user runs the code on their own data. > >> In fact, it feels to me that the trend has been towards >> non-privileged installs. Npm, nvm, node, chrome, pyenv, JetBrains products, >> slack (via snap), docker-desktop, virtualbox --- none of them require root >> privileges and all of them put config information under the user directory. > > Yes, but privilege and system vs user are not entirely the same thing. > And I would argue that the trend to containerization in various forms is > driven by a lack of discipline in software engineering in terms of > stable APIs, leading to needing pinned dependencies far more than you > would have 15 years ago. So I don't think it's really a good thing; it > just is how it is. But that's off topic really, and I think the path > you are heading down is going to be fine. > > -- > 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 weewx-development+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-development/rmitu39f280.fsf%40s1.lexort.com. -- 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 weewx-development+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/D70F890C-0102-4D68-8D00-DB8A8342E981%40gmail.com.
