| 1 |
On 9/13/06, Alan E. Davis <lngndvs@×××××.com> wrote: |
| 2 |
> It took a tremendous amount of time, months, to setup all of these |
| 3 |
> packages; maintenance of the system also demands not only a fast |
| 4 |
> network connection, but also a lot of time. It's not going to be easy |
| 5 |
> to reinstall this system in it's current form. Perhaps it's |
| 6 |
> necessary, however. |
| 7 |
|
| 8 |
I think at this point you have two options: |
| 9 |
|
| 10 |
1. Reinstall the system using the curernt 2006.1 AMD media. |
| 11 |
|
| 12 |
Advantages: |
| 13 |
- you can use the GRP binary packages to do a quick update. |
| 14 |
- you avoid recompiling everything for the gcc update |
| 15 |
- updating to current should be a fairly small change |
| 16 |
|
| 17 |
Disadvantages: |
| 18 |
- You need to be sure to backup your configuration files, or you may |
| 19 |
lose something that took a long time to get right. |
| 20 |
- If you have/make a lot of changes to USE, you may have a lot of |
| 21 |
things that need to be rebuilt after you are "done" with the install. |
| 22 |
|
| 23 |
If you do this, be sure to backup your configuration files, especially |
| 24 |
/etc/portage, /etc/make.conf. Plus you probably want to keep |
| 25 |
/var/lib/portage/world as well. |
| 26 |
|
| 27 |
2. Remove ~amd64 from keywords, and basically follow the gcc upgrade |
| 28 |
guide, since you probably need to udpate to gcc 4.1 anyway. |
| 29 |
|
| 30 |
Advantages: |
| 31 |
- It's relatively easy to see what things are going to be downgraded, |
| 32 |
so you can decide what needs to be added to package.keywords. |
| 33 |
- Your configuration files will be protected by CONFIG_PROTECT. |
| 34 |
|
| 35 |
Disadvantages: |
| 36 |
- You end up doing an emerge -e world, which is going to take quite a |
| 37 |
while to execute. |
| 38 |
|
| 39 |
|
| 40 |
>From a general perspective on running some ~arch packages on an |
| 41 |
otherwise stable system, how successful that is usually depends on how |
| 42 |
many ~arch packages you have. ~arch packages tend to depend on other |
| 43 |
~arch things, so there is a viral effect that leads some people to |
| 44 |
give up and use ~arch for the entire system. Using the |
| 45 |
~cate-gory/package-ver.s.ion syntax can help here, as it only allows |
| 46 |
the ~arch keyword for specific versions or -r releases. |
| 47 |
|
| 48 |
HTH, |
| 49 |
-Richard |
| 50 |
-- |
| 51 |
gentoo-user@g.o mailing list |
Archives