Sure. So a weewx update requires: - updating weewx in python-land via pip - resynching the weewx-data tree to catch up to the pip-installed content - restarting the daemon (maybe/possibly/usually)
FWIW, this one seems like an opportunity for a wrapper script, regardless of language selected. The catch-22 of course is what if a weewx upgrade changes the wrapper itself too in the first step, as well as dealing with what if step-N failed for whatever reason. But a "weectl software upgrade" command for a wrapper would be kind of nice if that's reasonable. I also wonder if 'weewx station upgrade' isn't super clear terminology either, but I don't have a better suggestion there. What bad happens if they answer 'no' to the prompt, for example ? Also, can we pass it a --yes switch like apt-get so we can fully script an upgrade and/or upgrade-skins ? On Sunday, January 29, 2023 at 6:16:30 PM UTC-8 Tom Keffer wrote: > On Sun, Jan 29, 2023 at 5:51 PM Vince Skahan <[email protected]> wrote: > >> That's going to confuse folks. An upgrade can reasonably be assumed to >> actually do it all shouldn't it ? >> >> Is there any way to make it do the right thing in one step ? >> > > Nope. pip does not allow you to freely roam the file system making > changes. Recall our earlier conversation about this. > > The only possibility is to come up with a shell script that invokes pip, > then follows up with "weectl station upgrade". Let me think about that. > -- 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/998ad96c-129b-4b3f-a883-2678473d707bn%40googlegroups.com.
