1 |
On Thu, 30 Mar 2006 08:30:17 +0900 |
2 |
Jason Stubbs <jstubbs@g.o> wrote: |
3 |
|
4 |
> On Thursday 30 March 2006 01:21, Marius Mauch wrote: |
5 |
> > Marius Mauch schrieb: |
6 |
> > > So after manifest2 is in, I'll revive the other issue that IMO is |
7 |
> > > a requirement for 2.1: enforcing dependencies needed to use the |
8 |
> > > tree (see old threads or glep44 for reasoning). |
9 |
> |
10 |
> Can you summarise the reasoning again please? |
11 |
|
12 |
a) avoid massive breakage when certain new features are introduced |
13 |
(past examples being cascading profiles or new-style virtuals) |
14 |
b) similar to a) allow people to use new features without having to |
15 |
wait for a year or two |
16 |
|
17 |
> > - at sync time first check the tree format of the remote tree, if |
18 |
> > we can't handle it the sync is aborted |
19 |
> |
20 |
> While I haven't checked over the code at all, the point above above |
21 |
> sounds problematic. What happens if the a user installs the latest |
22 |
> with this patch and then doesn't sync for three years? The tree may |
23 |
> then require a later portage but the user can't sync to be able to |
24 |
> emerge a later portage. |
25 |
|
26 |
!!! This upgrade might fail, in that case please read the |
27 |
!!! following documents for help: |
28 |
!!! http://www.gentoo.org/proj/en/portage/doc/common-problems.xml |
29 |
!!! |
30 |
http://www.gentoo.org/proj/en/portage/doc/manually-fixing-portage.xml |
31 |
|
32 |
These docs will then tell the user about the following options |
33 |
a) use the secret override |
34 |
b) manually update the tree with wget+tar |
35 |
c) perform an manual update (as in wget portage-version.tar.bz2, ...) |
36 |
|
37 |
That should be an extreme exception though, there will be some rules |
38 |
regarding format bumps (like "only use formats where that haven been |
39 |
supported by stable portage for n months"). |
40 |
|
41 |
Marius |
42 |
-- |
43 |
gentoo-portage-dev@g.o mailing list |