Vince Skahan <vinceska...@gmail.com> writes: > Huh ? > > Packages have been available for debian(ish) and redhat(ish) operating > systems for a number of years. Those packages install the > prerequisite/corequisite packages that are needed to make weewx work and > install things where those operating systems install things. What exactly > is missing there currently ? > > I'd suggest almost all of the (newbie) pi users are using the packaged > version these days, based on the questions we see.
Thanks for taking the time to write back to me. I was guessing this wasn't the case, because the weewx setup.py install seemed like it would be hard to make a package out of. I now understand that the Linux packages don't use setup.py to install, which clears up a lot. > Upgrades have always just plain worked in my experience, for both > debian(ish) and redhat/fedora systems, regardless of whether you were > packaged or setup.py for your installation method.....as long as you stick > with the method of installing weewx you picked. So pretty obviously the Debian/RH packages are splitting the config updating from the "put the scripts in the destdir" script -- which was clear to me needed to be done, but it felt like fighting city hall since that's what setup.py install does. Now that I get that setup.py isn't used, my fog of dissonance is lifted. > The structure of weewx.conf is a bit difficult to script around due to its > configobj origins, but lots of work has been done to make the items therein > unique enough to let you run sed inline (or use ansible, etc.) against that > file to salt to taste. Most people shouldn't have to do anything for a > vanilla weewx system other than install the package interactively and > answer the prompts it provides. Agreed that the config setup/merge code works well - it has for me for manual installs. > The extension installer also helps a lot, permitting you to add/delete > skins+extensions with one command. So if you have well-formed skins and > extensions you might never need to even edit weewx.conf - but of course > some require a 'lot' of touch labor to tweak to your liking. That's the > skins/extensions bug/feature, not the core weewx product's limitations. I am guessing then that these are not dealt with by the packaging system, even though they feel to me like they are packages that depend on weewx. Is that right? > FWIW, I can build my whole system totally scripted using either setup.py > 'or' a packaged weewx by installing weewx and running sed inline on the > weewx.conf file, then resetting the daemon. That's not bad. setup.py is interactive, so I'm guessing you are passing the flag to avoid that and then editing weewx.conf from the release version to your local values. > While I'd also like to see a more modular weewx.conf structure, that's come > up a lot in the past and the decision was made to stay the course as-is > there. But sure I'd agree that moving to a less python configobj kind of > structure to something more mainstream even if it's a ini file would be > cool to see, but there are a zillion plus/minus things there as well. It > was an interesting conversation way back when.... I can see the point, but I was not trying to address the config file format. It's the conflation of "install" and "configure" that I was really getting at. -- 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/rmiwofsecaf.fsf%40s1.lexort.com.
