Void Linux discussion
 help / color / mirror / Atom feed
From: bougyman <boug...@rubyists.com>
To: voidlinux@googlegroups.com
Subject: Re: Void-Stable?
Date: Mon, 6 Apr 2015 18:33:03 -0500	[thread overview]
Message-ID: <CA+cVzNXgO9ikzjX0T1O8NQxs8TjG9WaLBcXBfGXECwCLbo0PPA@mail.gmail.com> (raw)
In-Reply-To: <fb1ba803-267c-43eb-8805-88600b5d19a5@googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]

I would also get output of 'these packages have security updates' in the
timeframe.

bougy

On Mon, Apr 6, 2015 at 6:16 PM, bougyman <boug...@rubyists.com> wrote:

>
>   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
> <https://groups.google.com/d/msgid/voidlinux/fb1ba803-267c-43eb-8805-88600b5d19a5%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

[-- Attachment #2: Type: text/html, Size: 2649 bytes --]

  reply	other threads:[~2015-04-06 23:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06 23:16 Void-Stable? bougyman
2015-04-06 23:33 ` bougyman [this message]
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=CA+cVzNXgO9ikzjX0T1O8NQxs8TjG9WaLBcXBfGXECwCLbo0PPA@mail.gmail.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).