As long as it's not destructive to run the new version on an old setup, I'd
not do anything special with @pkgpath, let the old update to the new as
normal, and people can pkg_delete the new and add the old if needed.
I'd probably just add a MESSAGE or maybe even just an FAQ entry rather than
@ask-update as it should be easy enough to recover as the old version is
available. @ask-update stops non-interactive updates from working.
--
Sent from a phone, apologies for poor formatting.
On 10 November 2024 14:00:11 Daniel Jakots <[email protected]> wrote:
On Sun, 10 Nov 2024 11:22:41 +0000, Stuart Henderson
<[email protected]> wrote:
server-old and server maybe?
Sure. What should be the upgrade port wise?
Is an @ask-update a la postgresql enough?
Only super old setups are impacted. People who started using minio
'recently' are fine, e.g.
https://marc.info/?l=openbsd-ports&m=170550900118060&w=2
Or should all users be moved to use the 'server-old' line and leave them
the task to check if their setup is compatible with recent minio and
manually upgrade to 'server'?
