With the existence of the void daily package archive, I've been bouncing around an idea about how someone (some admin/architect/enterprise) could maintain

their own 'stable' release cycle of void. If upon initial configuration the repos are set to an archive with a date stamp, and the user has a way to validate that moving

from that datestamp to ### future datestamp doesn't (potentially) break any functionality, they can safely choose an upgrade path. for instance.

I install on 2015-03-26 and lock the repository to the archive snapshot of that date

on 2015-04-26 I run *magic-command* and ask if upgrading to current (2015-04-26) would (potentially) break any installed packages.

I get output about any important breaking changes (to xbps, etc) which may require an 'upgrade this first' action or 'remove these' actions.

I get output that may just say: 'Upgrade to 2015-04-01 first, then to 2015-04-15, then 2015-04-26' (or does this automagically?)

Thoughts?

bougy

--
You received this message because you are subscribed to the Google Groups "voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+...@googlegroups.com.
To post to this group, send email to void...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/fb1ba803-267c-43eb-8805-88600b5d19a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.