Void Linux discussion
 help / color / mirror / Atom feed
From: "Stefan Mühlinghaus" <"master..."@googlemail.com>
To: voidlinux@googlegroups.com
Subject: Re: Void-Stable?
Date: Tue, 7 Apr 2015 01:34:28 -0700 (PDT)	[thread overview]
Message-ID: <7887d857-00a3-4e7b-9f5e-435612034ac5@googlegroups.com> (raw)
In-Reply-To: <fb1ba803-267c-43eb-8805-88600b5d19a5@googlegroups.com>


[-- Attachment #1.1: Type: text/plain, Size: 985 bytes --]

I suppose someone could maintain a series of "stable" repositories that are 
(at time of creation) essentially copies of the main void repositories. A 
simple shell script could be used switch releases on the users system. 
Security updates may then simply be backported into previous releases.

However, to ensure that updates between the releases do not break anything 
would be a HUGE commitment, very time-consuming and with limited resources 
(time, manpower) there is still always the possibility that some problems 
will be overlooked. An additional mechanism would probably need to be 
implemented to (semi)automatically deal with any update conflicts that 
cannot be avoided in the packages.

At that point you would need to update step by step, one release at a time, 
even if your systems current state is several releases back. Otherwise 
every new release has to be tested/fixed for all supported prior releases, 
which would multiply the effort to do so.

[-- Attachment #1.2: Type: text/html, Size: 1026 bytes --]

  parent reply	other threads:[~2015-04-07  8:34 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 ` Void-Stable? bougyman
2015-04-07  0:34 ` Void-Stable? Kevin Berry
2015-04-07  8:34 ` Stefan Mühlinghaus [this message]
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=7887d857-00a3-4e7b-9f5e-435612034ac5@googlegroups.com \
    --to="master..."@googlemail.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).