1 |
On Tue, 2004-02-03 at 15:33, Paul de Vrieze wrote: |
2 |
> On Tuesday 03 February 2004 21:06, Chris Gianelloni wrote: |
3 |
> > > |
4 |
> > > I'm probably missing something, but having an rsync server set up to |
5 |
> > > return the stable trees seems rather silly, since those trees never |
6 |
> > > change (only the "updates" trees change). A tarball would seem much |
7 |
> > > simpler, and the appropriate tarball could be included on the livecd for |
8 |
> > > that release. |
9 |
> > |
10 |
> > Actually, the rsync server should check the variable VERSION (or |
11 |
> > whatever) and update accordingly. Maybe we could do something as simple |
12 |
> |
13 |
> Stable does not change per defenition, so a tarbal is way more efficient than |
14 |
> an rsync server calling home once in a while to check that indeed, nothing |
15 |
> changed. |
16 |
> |
17 |
> > as putting a 2004.0-release file in the /usr/portage, so when VERSION |
18 |
> > changes to 2004.1, they no longer match and the 2004.1 tree is rsync'd |
19 |
> > instead. |
20 |
|
21 |
I guess that seems like it would work just as well. In fact, I agree |
22 |
that the tarball idea would be a better solution. |
23 |
|
24 |
> That can be done with tarballs just as well. However don't expect syncing a |
25 |
> tree to be the only thing to be done when updating. In general updating is |
26 |
> more involved. If you say hook off your gentoo machine for a year and then |
27 |
> try to update it is not at all trivial. You need to ensure that you update |
28 |
> things in the right order, and sometimes even need to apply some force. We |
29 |
> can find out that order in advance to make it easy for users, but don't |
30 |
> pretend it is trivial. |
31 |
|
32 |
I didn't mean to make it sound trivial. I know it would not be. I was |
33 |
just trying to make it simpler for the sake of discussion at this time. |
34 |
|
35 |
-- |
36 |
Chris Gianelloni |
37 |
Developer, Gentoo Linux |
38 |
Games Team |
39 |
|
40 |
Is your power animal a pengiun? |