(I've been running weewx for about 1.5 years under NetBSD on i386 and then RPI3, using pkgsrc to provide the dependencies.)
I created a pkgsrc package for weewx in pkgsrc-wip, and there are some awkward things about it. Part of the reason was to capture the dependencies to avoid having to manually manage that I need Pillow, etc. Part of it is that I think software should in general be packaged and that almost all uses of 99% of software is via packaging systems. I realize that the maintainers of many pieces of software think their software is special (all software is!) and that people should do things by hand and pay close attention. I can of course see the point, especially for weewx, but in general this does not scale. The main difficulty I encountered is the handling of weewx.conf; the install is interactive and there is a notion of merging updated config files. From a packaging viewpoint, it would be really nice to be able to install weewx (to an empty place) non-interactively at package creation time, register the config file as an example, and then somehow be able to separately invoke the config file merging when the package is installed. I have sort of dealt with this, but not entirely. The escond issue is that weewx does not follow the usual conventions for installation of executable programs, python files used by programs, config files, etc. I have dealt with this by installing to /usr/pkg/weewx (as weewx_home), as it doesn't seem useful for me to try to rearrange things. >From my experience, I am guessing that essentially no one is using weewx from packaging, and that probably even in Debian, Ubuntu, FC, etc. there are not packages. I am curious if there are packages, and if anyone who worked on those packages has words of wisdom. I also wonder what people think of splitting the process of installing the default config file (I put it in weewx.conf.DIST, intending that to be owned by the packaging system and never changed by the user) from the process of creating the user's config file and merging that config file. This update could then be hooked into the package installation process. That should allow people to install weewx from packaging instead of manually from a git checkout or tarball, and upgrade, while still having the same semantics. Greg -- 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/rmiftmqs1r4.fsf%40s1.lexort.com.
