1 |
Zac Medico posted on Tue, 17 Feb 2015 00:37:12 -0800 as excerpted: |
2 |
|
3 |
> It is not necessary to migrate an |
4 |
> existing PKGDIR to the new layout, since portage is capable of working |
5 |
> with a mixed PKGDIR layout, where packages using the old layout are |
6 |
> allowed to remain in place. |
7 |
|
8 |
[...] |
9 |
|
10 |
> There is currently no automated way to prune old builds from PKGDIR, |
11 |
> although it is possible to remove packages manually, and then run |
12 |
> 'emaint --fix binhost' to update the ${PKGDIR}/Packages index. |
13 |
> |
14 |
> It is not necessary to migrate an existing PKGDIR to the new layout, |
15 |
> since portage is capable of working with a mixed PKGDIR layout, where |
16 |
> packages using the old layout are allowed to remain in-place. |
17 |
> |
18 |
> There is currently no automated way to prune old builds from PKGDIR, |
19 |
> although it is possible to remove packages manually, and then run |
20 |
> 'emaint --fix binhost' update the ${PKGDIR}/Packages index. |
21 |
|
22 |
[...] |
23 |
|
24 |
|
25 |
Reading this gave me a distinct sense of deja vu reading this. ... =:^P |
26 |
|
27 |
(After editing a bit, the second "reading this" deliberately left in |
28 |
place. =:^) |
29 |
|
30 |
-- |
31 |
Duncan - List replies preferred. No HTML msgs. |
32 |
"Every nonfree program has a lord, a master -- |
33 |
and if you use the program, he is your master." Richard Stallman |