1 |
Alan McKinnon wrote: |
2 |
> On Wednesday 20 December 2006 21:09, Benno Schulenberg wrote: |
3 |
> > Mark Knecht wrote: |
4 |
> > > At that point it's gone. I cannot put into an overlay |
5 |
> > > what I don't have. Probably most frustrating has been that I |
6 |
> > > don't know it will be removed until it's been removed. |
7 |
> > |
8 |
> > You could, as soon as you have a system in a working state, tar |
9 |
> > up the entire /usr/portage tree, [...] |
10 |
> |
11 |
> No, no, no that's waaaaaaaay too much work. |
12 |
|
13 |
On the contrary, it's very little work: just a simple tar command. |
14 |
But the tarball will eat loads of disk space when not excluding |
15 |
distfiles. |
16 |
|
17 |
> Archive a portage tree by all means. But if an ebuild is removed |
18 |
> that a user want to keep, the solution is so simple it's amazing. |
19 |
> Copy the ebuild to /usr/local/portage [...] |
20 |
|
21 |
But he can't: the ebuild is gone. That is the case we're trying to |
22 |
solve here: he has emerged a newer version of a package, finds it |
23 |
doesn't work correctly, wants to go back to the previous version, |
24 |
but seess that that version is gone. How to get it back? One way |
25 |
is to get it from viewcvs on the net. Another way is to keep a copy |
26 |
of all the ebuilds yourself. It's a big waste of space, but it is |
27 |
simple, no searching on the web required. |
28 |
|
29 |
The best way, of course, is to use the binary package thing. Mark: |
30 |
add EMERGE_DEFAULT_OPTS="-b" to your /etc/make.conf. This will |
31 |
tell emerge to also build a binary package for every package that |
32 |
you emerge. Whenever you find that an upgrade of some package was |
33 |
unfortunate, do an 'emerge -K =package-x.y.z' with the exact |
34 |
version number you want to restore, and done. No manual tarring |
35 |
and untarring required, emerge does it all. |
36 |
|
37 |
Benno |
38 |
-- |
39 |
gentoo-user@g.o mailing list |