From: bougyman <boug...@rubyists.com>
To: voidlinux@googlegroups.com
Subject: Void-Stable?
Date: Mon, 6 Apr 2015 16:16:05 -0700 (PDT) [thread overview]
Message-ID: <fb1ba803-267c-43eb-8805-88600b5d19a5@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1013 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 1169 bytes --]
next reply other threads:[~2015-04-06 23:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 23:16 bougyman [this message]
2015-04-06 23:33 ` Void-Stable? bougyman
2015-04-07 0:34 ` Void-Stable? Kevin Berry
2015-04-07 8:34 ` Void-Stable? Stefan Mühlinghaus
2015-04-07 8:47 ` Void-Stable? Christian Neukirchen
2015-04-08 4:53 ` Void-Stable? Juan RP
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb1ba803-267c-43eb-8805-88600b5d19a5@googlegroups.com \
--to="boug..."@rubyists.com \
--cc=voidlinux@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).