1 |
Hi! |
2 |
|
3 |
On Sun, 17 Jan 2010, Ciaran McCreesh wrote: |
4 |
> > 1) portage/pkgcore support the PMS defined vdb2 while paludis doesn't |
5 |
> > 2) portage/pkgcore are invoked modifying the livefs; vdb1, vdb2 is |
6 |
> > updated. |
7 |
> > 3) paludis is invoked. vdb1 is updated, vdb2 is not |
8 |
> > 4) portage and pkgcore now cannot rely upon vdb2, since vdb1 now |
9 |
> > contains extra modifications due to paludis not supporting vdb2. |
10 |
> |
11 |
> No, we'd not do it that way. If we're ditching VDB, the only sane way |
12 |
> to do it is to ditch it with an rm -fr when creating the new layout. |
13 |
> Keeping two sets of data around is going to lead to breakage no matter |
14 |
> how well we do things. |
15 |
|
16 |
Please also provide a downgrade path, i.e. a way to go back from |
17 |
the new DB version to the current one should it be necessary (if |
18 |
there is no such path, Murphy will see to it that the new format |
19 |
breaks in interesting[0] ways). |
20 |
|
21 |
Just my 0.0139304869 Euros (at current exchange rate), |
22 |
Tobias |
23 |
|
24 |
[0] Chinese-style interesting |
25 |
|
26 |
-- |
27 |
printk("whoops, seeking 0\n"); |
28 |
linux-2.6.6/drivers/block/swim3.c |