a few thoughts: 1) a setup.py install should not touch any part of the system other than the directory in which you install weewx. if you want udev rules, logrotate, rsyslog, init.d/systemd, PATH, or anything else you do it yourself. the weewx setup.py is not a typical python installation - it is a way to install weewx into a single directory.
2) a package install really should use an unprivileged user to run weewx, not root. install as root, but run as unprivileged user. (i've sat down to do this a few times, but inevitable stop because of testing all of the update/upgrade corner cases) 3) a package install should install all of these items, in a way that works out-of-the-box and degrades gracefully: - init.d/systemd - udev rules (but they must not conflict with anything else user might have) - rsyslog, logrotate, logwatch in /etc/weewx, ready to go but not enabled - weewx user+group so weewx is run as unprivileged user ideally the package install would also probe the system for known hardware (if it is a first-time install), and automatically choose the right driver. 4) documentation should always use relative path, i.e., just the command, not the full path to command. you can make a single comment about possible paths if you want, but that has already been done in the user guide and a dedicated wiki page. do not pollute the rest of the documentation with that confusion. 5) in the docs, do not preface instructions with 'sudo' unless you mean it, and be sure to preface with 'sudo' when you know that privilege escalation is required. 6) for any upgrade, i don't even like the fact that the weewx installer touches my config files (especially when it just mangles comments). and the dependency on a version string in the weewx.conf file is a fail waiting to happen. it is important to distinguish between documentation - something that shows the concepts - versus recipes - something that you might copy-paste to restore your system, or something that is bespoke for a specific configuration. given the multiple platforms and experimental nature of weewx, there will never be one recipe to rule them all. i'm pretty settled about (1) - like tom said, if a user does setup.py, that user must at least understand PATH. if someone does not understand PATH, just refer him/her to the PATH wiki page. sorry for expanding the scope of this thread, but this is a spaghetti problem, not a meatball problem. m -- 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/7100c210-3e55-4752-bef6-e028f2ded723n%40googlegroups.com.
