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

On Monday 02 February 2004 20:53, Kurt Lieber wrote:
> On Mon, Feb 02, 2004 at 12:27:08PM -0600 or thereabouts, Brian Jackson 
wrote:
> > One problem I have with this is that it says all ebuilds should
> > remain in the tree for a minimum of one year. 4 releases a year, and
> > every package in the tree is going to have 4 versions that can't be
> > cleaned out for at least a year. Not to mention that it's going to
> > be hard to get developers in to the mindset of saving old ebuilds
> > when we've been beating them ruthlessly about keeping portage clean
> > for the past 6 months at least. Do you have any ideas about how to
> > deal with this?
>
> Valid point.  One suggestion I would have would be to add a "date
> created" stamp to each ebuild (or perhaps this information is already
> there in the header somewhere).  Then, we can track that info across
> the whole stable tree so the developer wouldn't have to worry about
> it.
>
> That is to say that, once it makes it into the stable tree, the
> developer isn't responsible for ensuring it stays there for a year --
> it's up to the maintainers of the stable tree (gentoo-server unless
> releng wants the job).
>
> I also like this solution because it would allow us to do useful
> things like publish a schedule of when various ebuilds will be retired
> so users can check them ahead of time and plan accordingly.

I think it should be mainly the responsibility of the administrators of 
the systems running stable to initiate an update. It is at most 4 times 
per year, so it shouldn't be a big hurdle. If you would automatically 
update after 3 months it would lose most of the advantages of having a 
stable tree in the first place.

Paul

- -- 
Paul de Vrieze
Gentoo Developer
Mail: [EMAIL PROTECTED]
Homepage: http://www.devrieze.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAH3MObKx5DBjWFdsRAoiQAKDTZJV8Xp4KXpjoBrY20UK5vkzzOQCgvOh8
w7ttj+FM1J/myu2zlnfUUyY=
=2uy6
-----END PGP SIGNATURE-----

--
[EMAIL PROTECTED] mailing list

Reply via email to