| 1 |
On Sun, 21 Jan 2007 14:25:21 -0600, Boyd Stephen Smith Jr. wrote: |
| 2 |
|
| 3 |
> > Also, what commands would a person have to use to make use of those |
| 4 |
> > buildpkg's? So far, I have not needed one. < says prayer > That |
| 5 |
> > assumes portage is what is screwed up to begin with. |
| 6 |
> |
| 7 |
> All you need is tar. You simply extract the compressed tarball over |
| 8 |
> your root file system and the package is installed, but not entered |
| 9 |
> into the vdb (so, it wouldn't be a bad idea to re-emerge it once you |
| 10 |
> get portage back up). |
| 11 |
|
| 12 |
Remember that tar doesn't respect $CONFIG_PROTECT, so it may overwrite |
| 13 |
your carefully crafted configuration files in /etc. Og course, if you're |
| 14 |
sensible enough to keep binary packages of the most important apps |
| 15 |
around, you're more than sensible enough to have a backup of /etc :) |
| 16 |
|
| 17 |
You may also want to consider keeping binary packages of some of the |
| 18 |
larger (as i compile time) not-quite-essential packages. Keeping binaries |
| 19 |
of xorg-server, kdelibs etc. may help you get going again more quickly |
| 20 |
after a broken upgrade or other borkage. If you use openoffice, as |
| 21 |
opposed to openoffice-bin, keeping a package fo that goes without saying. |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Neil Bothwick |
| 26 |
|
| 27 |
If at first you don't succeed, skydiving is not for you. |
Archives