| 1 |
On Monday 06 April 2009, Kyle Liddell wrote: |
| 2 |
> On Sun, Apr 05, 2009 at 03:48:19PM -0400, Richard Freeman wrote: |
| 3 |
> > FYI - quickpkg is your friend in these kinds of situations. You can |
| 4 |
> > then back out pretty quickly. However, if you start merging packages |
| 5 |
> > left and right after a glibc upgrade be VERY careful about downgrading |
| 6 |
> > your glibc - that can very easily break things. If glibc is the only |
| 7 |
> > thing that you've upgraded I suspect a downgrade would go ok. |
| 8 |
> |
| 9 |
> If you've got a few GB of disk free, you could always take the "nuke it |
| 10 |
> from orbit" approach: tar up / before you do the upgrade. That's saved me |
| 11 |
> many a time when I've done something stupid and ended up without a working |
| 12 |
> copy of gcc/python/whatever, and didn't feel like playing games with |
| 13 |
> portage to get back to work. |
| 14 |
|
| 15 |
just turn on the binary package option (put buildpkg into FEATURES). That way |
| 16 |
you have nice packages of all packages you ever installed - if something is |
| 17 |
nuked all you need is a working tar+bzip |
Archives