1 |
> There is one use-case that I am aware of against removing old versions of 4.*, |
2 |
> but I haven't seen it in the tree for a while - other folk might be more aware |
3 |
> of it: Ability to take DB files from other systems and read them sanely / |
4 |
> migrate them to new versions. |
5 |
|
6 |
Yep, subversion comes to mind on this one. Though, this isn't forcing anyone to |
7 |
uninstall their db versions, but simply removing them from the portage. Granted, it |
8 |
does make it more difficult to migrate db version backends, but since the ebuilds in |
9 |
question will be available from the CVS attic on cvsweb, I think the benefit |
10 |
outweighs the harm in removing them. |
11 |
|
12 |
> Here's a set of stuff of everything that looks for a specific version of 4.*. |
13 |
|
14 |
Thanks for this list. It seems that the removal of 4.0* and 4.1* are probably okay, |
15 |
based on this information. |
16 |
|
17 |
I imagine we'll go through a normal 30 day package.mask/removal procedure when the |
18 |
time comes. |
19 |
|
20 |
Caleb |
21 |
|
22 |
-- |
23 |
gentoo-dev@g.o mailing list |