| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Monday 02 February 2004 20:53, Kurt Lieber wrote: |
| 5 |
> On Mon, Feb 02, 2004 at 12:27:08PM -0600 or thereabouts, Brian Jackson |
| 6 |
wrote: |
| 7 |
> > One problem I have with this is that it says all ebuilds should |
| 8 |
> > remain in the tree for a minimum of one year. 4 releases a year, and |
| 9 |
> > every package in the tree is going to have 4 versions that can't be |
| 10 |
> > cleaned out for at least a year. Not to mention that it's going to |
| 11 |
> > be hard to get developers in to the mindset of saving old ebuilds |
| 12 |
> > when we've been beating them ruthlessly about keeping portage clean |
| 13 |
> > for the past 6 months at least. Do you have any ideas about how to |
| 14 |
> > deal with this? |
| 15 |
> |
| 16 |
> Valid point. One suggestion I would have would be to add a "date |
| 17 |
> created" stamp to each ebuild (or perhaps this information is already |
| 18 |
> there in the header somewhere). Then, we can track that info across |
| 19 |
> the whole stable tree so the developer wouldn't have to worry about |
| 20 |
> it. |
| 21 |
> |
| 22 |
> That is to say that, once it makes it into the stable tree, the |
| 23 |
> developer isn't responsible for ensuring it stays there for a year -- |
| 24 |
> it's up to the maintainers of the stable tree (gentoo-server unless |
| 25 |
> releng wants the job). |
| 26 |
> |
| 27 |
> I also like this solution because it would allow us to do useful |
| 28 |
> things like publish a schedule of when various ebuilds will be retired |
| 29 |
> so users can check them ahead of time and plan accordingly. |
| 30 |
|
| 31 |
I think it should be mainly the responsibility of the administrators of |
| 32 |
the systems running stable to initiate an update. It is at most 4 times |
| 33 |
per year, so it shouldn't be a big hurdle. If you would automatically |
| 34 |
update after 3 months it would lose most of the advantages of having a |
| 35 |
stable tree in the first place. |
| 36 |
|
| 37 |
Paul |
| 38 |
|
| 39 |
- -- |
| 40 |
Paul de Vrieze |
| 41 |
Gentoo Developer |
| 42 |
Mail: pauldv@g.o |
| 43 |
Homepage: http://www.devrieze.net |
| 44 |
-----BEGIN PGP SIGNATURE----- |
| 45 |
Version: GnuPG v1.2.4 (GNU/Linux) |
| 46 |
|
| 47 |
iD8DBQFAH3MObKx5DBjWFdsRAoiQAKDTZJV8Xp4KXpjoBrY20UK5vkzzOQCgvOh8 |
| 48 |
w7ttj+FM1J/myu2zlnfUUyY= |
| 49 |
=2uy6 |
| 50 |
-----END PGP SIGNATURE----- |
| 51 |
|
| 52 |
-- |
| 53 |
gentoo-dev@g.o mailing list |
Archives