1 |
On Wednesday 20 December 2006 21:09, Benno Schulenberg wrote: |
2 |
> Mark Knecht wrote: |
3 |
> > At that point it's gone. I cannot put into an overlay |
4 |
> > what I don't have. Probably most frustrating has been that I |
5 |
> > don't know it will be removed until it's been removed. |
6 |
> |
7 |
> You could, as soon as you have a system in a working state, tar up |
8 |
> the entire /usr/portage tree, and then, when you find an upgrade |
9 |
> has broken an essential package, untar the ball over your new tree, |
10 |
> and re-emerge the old version of the package. Once a month or so, |
11 |
> when you find that also the newest tree gives you a working system, |
12 |
> you would tar up that /usr/portage instead and remove the old one. |
13 |
> This is the dead simple, brute force way, no overlay required. :) |
14 |
|
15 |
No, no, no that's waaaaaaaay too much work. |
16 |
|
17 |
Archive a portage tree by all means. But if an ebuild is removed that a |
18 |
user want to keep, the solution is so simple it's amazing. Copy the |
19 |
ebuild to /usr/local/portage in the correct directory structure. I |
20 |
maintain my own enlightenment-17 ebuilds, so to start I did this: |
21 |
|
22 |
mkdir -p /usr/local/portage/x11-wm |
23 |
cp -ar /usr/portage/x11-wm/e /usr/local/portage/x11-wm |
24 |
|
25 |
Run emerge. Simple as that. You might need to add an entry to |
26 |
package.mask so that portage won't use later versions in the main tree |
27 |
but that's all part of normal gentoo usage anyway |
28 |
|
29 |
There's a howto on gentoo.org that explains this in great detail. Use |
30 |
it, it's the way portage let's you keep old stuff around. |
31 |
|
32 |
alan |
33 |
-- |
34 |
gentoo-user@g.o mailing list |