Hello! @sthen,@landry,@gonzalo... thanks for your thoughts!
[email protected] (Gonzalo Rodriguez), 2021.05.28 (Fri) 23:09 (CEST): > > On 27. May 2021, at 16:15, Landry Breuil <[email protected]> wrote: > > > > Le Thu, May 27, 2021 at 01:20:10PM +0100, Stuart Henderson a écrit : > >> I'm not convinced this is a good idea. > >> > >> @ask-update is problematic because it blocks updates of packages unless > >> there's manual intervention. For someone who adds pkg_add -u to > >> rc.firsttime > >> or uses configuration management to update packages this adds things which > >> are awkward to automate. Ah, I didn't consider such a use case... > >> PostgreSQL is special because, in some cases, you need to take extra steps > >> *before* the upgrade. (pg_upgrade/postgresql-previous can't easily be made > >> to work with compiled add-on modules). Quite often you can't just install > >> the old postgresql package again because the compiled binaries won't always > >> run on the updated OS which is less of a problem with PHP. postgresql's @ask-update has saved me multiple times. I thought the same would be easy-peasy for nextcloud. Thanks for explaining the difference! > >> It is common for > >> ports to need extra steps after upgrading, there's nothing particularly > >> unusual about nextcloud in that respect. This does not match my experience, but you see the bigger picture! > > seconded, all nextcloud upgrades have always needed extra steps (eg occ > > upgrade as www user) since forever.. and i agree that @ask-update always > > leads to pain :) I wanted to prevent pain (users finding out that I forgot necessary steps after updates), not cause pain. I understand now that @ask-update is so bad it's really, really last ressort. Is there any less intrusive way of emitting a warning? And, beeing relatively new to running nextcloud, I am confident that I wont forget anymore :-) > Yup, probably is not the best or straight forward but still “faster” > and less problematic Thanks for maintaining the port! Marcus
