public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Barry Shaw <baz@scms.waikato.ac.nz>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Revisiting GLEP 19
Date: Wed, 21 Jul 2004 13:55:44 +1200	[thread overview]
Message-ID: <40FDCD20.6080302@scms.waikato.ac.nz> (raw)
In-Reply-To: <20040720131405.GW18023@mail.lieber.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


|
| So, with that said, thoughts, comments and other ideas are welcome.
|

So far most of the discussion seems to center around stable portage as
snapshots of the main tree taken at regular intervals.  These snapshots
contain only packages marked as stable, and only security updates are
applied to the snapshots.

It might be worth considering instead a model where a snapshot is taken
then only security patches are applied, with the exception that should a
particular version of an application become depreciated, it can then
also be upgraded (provided the upgraded version is also considered stable).

This would enable snapshots to last for a longer period (I think four a
year is going to be too much work), it prevents any requirement for
backporting (which I think is a bad idea as it makes ebuild maintainers
into application maintainers) and it would also make the maintenence of
older snapshots more viable as there would be less work to do in general.

Some of the current discussion on the length of time snapshots are
maintained is concerning as production servers, in my experience, remain
in the same state for years - a one year maintenence period is not long
enough (it would be for workstations however as these are easier to take
out of service for an hour or so and upgrade).

In reality, if a application on a production server reaches a state
where it is unmaintained in favour of a newer version, then its likely
that the admins would upgrade the application to the supported version.
~ Most responsible program maintainers provide upgrade paths anyways, so
as long non security related package upgrade wasn't forced on
subscribers to the stable tree, it shouldn't be too bad.  At the least
if such a change could be signalled, people would be prepared.

I guess what I'm describing isn't strictly an enterprise gentoo (which I
don't think the community has the resources to support), more of a
slowed down version of the main portage tree.  In my experience
maintaining a couple of hundred of gentoo machines centrally, its the
rapid pace of change in the main tree that causes problems.  We only
only upgrade packages for security reasons, but whenever we do this, we
are forced to upgrade a multitude of other packages because they've
dropped out of portage.  If we only had to upgrade packages for security
and depreciation reasons it would make for a much more stable
environment for the end users (which is what we're after ultimately) and
~ it would make maintenence more manageable.

Baz


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFA/c0gJvZkjpKMF2wRAiZXAKCAngA2ZVztXnGg0zXRmhtaqYGV5ACcDs5m
cO4fxnbFP+5ulb4CHfI6uN4=
=9/gh
-----END PGP SIGNATURE-----

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2004-07-21  1:55 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-20 13:14 [gentoo-dev] Revisiting GLEP 19 Kurt Lieber
2004-07-20 19:36 ` RNuno
2004-07-20 20:43 ` Dylan Carlson
2004-07-20 21:03   ` Tom Payne
2004-07-20 21:18     ` Kurt Lieber
2004-07-20 21:36     ` Dylan Carlson
2004-07-20 21:14   ` Olivier Crete
2004-07-20 21:41     ` Dylan Carlson
2004-07-20 22:06   ` Stuart Herbert
2004-07-20 22:50     ` Kurt Lieber
2004-07-21 14:53       ` Toby Dickenson
2004-07-20 22:58     ` Dylan Carlson
2004-07-21 20:00   ` Chris Gianelloni
2004-07-21 21:12     ` Olivier Crete
2004-07-21 21:39       ` Chris Gianelloni
2004-07-21 21:57       ` Michael Marineau
2004-07-22 12:24         ` Chris Gianelloni
2004-07-21  0:27 ` Michael Marineau
2004-07-21  0:54   ` Dylan Carlson
2004-07-21  1:07     ` Michael Marineau
2004-07-21  1:43       ` Dylan Carlson
2004-07-22 18:28       ` Martin Schlemmer
2004-07-21 16:13     ` Marius Mauch
2004-07-21 17:25       ` Dylan Carlson
2004-07-21 20:12     ` Chris Gianelloni
2004-07-21  1:55 ` Barry Shaw [this message]
2004-07-21  3:10   ` Michael Marineau
2004-07-21  6:50   ` Daniel Ostrow
2004-07-21 20:25     ` Chris Gianelloni
2004-07-21 20:21   ` Chris Gianelloni
2004-07-22  9:00     ` [gentoo-dev] " Duncan
2004-07-22 12:57       ` Chris Gianelloni
2004-07-21 12:39 ` [gentoo-dev] " Stuart Herbert
2004-07-21 12:56   ` Daniel Ostrow
2004-07-21 12:58   ` Toby Dickenson
2004-07-21 13:15     ` Stuart Herbert
2004-07-21 13:43       ` Jason Wever
2004-07-21 14:47         ` Carsten Lohrke
2004-07-21 15:08           ` Stuart Herbert
2004-07-21 15:45             ` Georgi Georgiev
2004-07-21 15:57               ` Ciaran McCreesh
2004-07-21 17:15             ` Carsten Lohrke
2004-07-23  4:22             ` Andrew Cowie
2004-07-21 20:51           ` Chris Gianelloni
2004-07-22 10:34             ` Carsten Lohrke
2004-07-22 13:06               ` Chris Gianelloni
2004-07-23 14:18                 ` Carsten Lohrke
2004-07-23 14:45                   ` Chris Gianelloni
2004-07-21 15:25         ` aeriksson
2004-07-21 15:36           ` Stuart Herbert
2004-07-21 16:34             ` aeriksson
2004-07-21 19:32               ` Stuart Herbert
2004-07-21 22:55                 ` Marius Mauch
2004-07-22  0:08                   ` Donnie Berkholz
2004-07-22  0:24                     ` Marius Mauch
2004-07-22  0:29                       ` Donnie Berkholz
2004-07-22 12:31                       ` Chris Gianelloni
2004-07-22 12:27                   ` Chris Gianelloni
2004-07-21 15:38           ` Lina Pezzella
2004-07-21 16:26             ` Dylan Carlson
2004-07-21 17:59               ` FRLinux
2004-07-21 16:39       ` Christian Birchinger
2004-07-21 20:42   ` Chris Gianelloni
2004-07-22  8:58     ` Stuart Herbert
2004-07-21 14:33 ` Lars Weiler

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=40FDCD20.6080302@scms.waikato.ac.nz \
    --to=baz@scms.waikato.ac.nz \
    --cc=gentoo-dev@lists.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