Gentoo Archives: gentoo-dev

From: Olivier Crete <tester@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] GLEP 19, reloaded (again)
Date: Mon, 09 Aug 2004 21:33:29
Message-Id: 1092087204.21951.9.camel@montreal
In Reply to: Re: [gentoo-dev] GLEP 19, reloaded (again) by Corey Shields
1 On Mon, 2004-08-09 at 16:12 -0500, Corey Shields wrote:
2 > On Monday 09 August 2004 03:56 pm, Olivier Crete wrote:
3 > > I'm re-proposing the tarball approach. When a stable release is made, a
4 > > tarball of the tree would be taken (while removing all of the non-stable
5 > > stuff and just keeping the arch keyworks if necessary..).. And then an
6 > > overlay rsync for security updates would be created.. This ensures the
7 > > long term survival of the release.. It also allows us to keep
8 > > "distributing" very old release (we know how many shops still use
9 > > redhat7 or even 6) without putting too much strain on the mirrors.
10 >
11 > This isn't a realistic solution. I think that moving away from the Portage
12 > tree as it is designed would be setting ourselves up to have a product with
13 > an end of life. With an evolving tree, some things may not change for a
14 > year, but when they DO change, an update should be possible without breaking
15 > the system or needing to start from scratch. The idea is not to freeze the
16 > tree permanently, but make it more "stable".
17
18 The whole point of a stable tree is to be stable.... rsync just doesn't
19 offer the same kind of guarantee.. Having security updates separate from
20 the "released" distribution is also a must imho. And this approach would
21 make that easy... This does not stop us from adding updates to the
22 overlay, it just makes it much easier for admins to control which
23 updates they want and which ones they dont...
24
25
26 > > Why do we need something as complex as profiling? And something that
27 > > requires work from every maintainer
28 >
29 > Profiling makes it such that we won't need work from every maintainer.
30
31 The idea of profiles (if I understand it correctly) is that every
32 package that is part of stable must be added to a file (thousands of
33 them).. And then every maintainer must make sure that he does not delete
34 the stable package for every arch in every version. We already see
35 people deleting the stable versions for less used arches... And if
36 stable uses a separate tree, then there is really no point to profiles..
37
38 > > Rsync is expensive for servers.. lets keep it down to the minimum. Its
39 > > much easier to get ftp/http mirrors than rsync...
40 >
41 > This is not true. We have MANY more rsync mirrors than we have source
42 > mirrors. The problem here is that most people don't have the disk space
43 > required for a distfiles mirror, whereas an rsync (portage) mirror is easy.
44 > I envision "enterprise" systems as needing to sync the tree less, especially
45 > if there are fewer updates expected. The rsync issue really isn't an issue
46 > (and I'm not a fan of rsync by any means).
47
48 We may have more rsync mirrors than source mirrors, but I'm sure that if
49 we offered the options of having stable mirrors without distfiles (just
50 the CD and portage tarballs), we'd have tons of those. (The new policy
51 of not having cds for p2,p3,p4,p68 really does help too imho)..
52
53 --
54 Olivier CrĂȘte
55 tester@g.o
56 Gentoo Developer
57
58
59 --
60 gentoo-dev@g.o mailing list

Replies

Subject Author
Re: [gentoo-dev] GLEP 19, reloaded (again) Corey Shields <cshields@g.o>