public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bill Kenworthy <billk@iinet.net.au>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Improving stability - checkpoints
Date: 20 Apr 2002 14:08:51 +0800	[thread overview]
Message-ID: <1019282931.24013.6.camel@rattus> (raw)
In-Reply-To: <3CC0CF44.8050303@gentoo.org>

One item I have not seen is the possibility of auto-rewinding something
like the libpng problem back to a working system.  CVS is a case in
point - when a build is broken, go back a version and build again. 
Williams checkpoint idea sounds similar to CVS in the way you can
specify versions.

Now this would be a *real* advance in taking some of the risk out of
bleeding edge for all users, average and developer.

BillK


On Sat, 2002-04-20 at 10:15, William McArthur wrote:
> [Sorry if this is a duplicate, I'm currently demonstrating a severe lack 
> of email skills.]
> 
> The other day there was a discussion on IRC about improving the 
> stability of the distro as a whole. The popular idea at the time was a 
> stability metric applied to each package based on a few things. The 
> following is my thoughts on how to improve the situation with minimal 
> developer effort.
> 
> First, I don't think the stability metric idea won't have it's desired 
> effect. The libpng problems would not be prevented with a stability 
> metric. The problem was not with the package specificlly but the 
> interaction between pacakges. Specifically packages that linked with 
> libpng and expected libpng-1.0.* .




  reply	other threads:[~2002-04-20  6:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-20  2:15 [gentoo-dev] Improving stability - checkpoints William McArthur
2002-04-20  6:08 ` Bill Kenworthy [this message]
2002-04-20 10:58   ` Terje Kvernes

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=1019282931.24013.6.camel@rattus \
    --to=billk@iinet.net.au \
    --cc=gentoo-dev@gentoo.org \
    /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