public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Update or Install again? Testing vs. stable?
Date: Wed, 13 Sep 2006 22:03:09 -0700	[thread overview]
Message-ID: <7573e9640609132203y30cd0d90m1e7cb1ef6c7265d0@mail.gmail.com> (raw)
In-Reply-To: <7bef1f890609132033m307ce494g82166dd530fa8fe2@mail.gmail.com>

On 9/13/06, Alan E. Davis <lngndvs@gmail.com> wrote:
> It took a tremendous amount of time, months, to setup all of these
> packages; maintenance of the system also demands not only a fast
> network connection, but also a lot of time.  It's not going to be easy
> to reinstall this system in it's current form.  Perhaps it's
> necessary, however.

I think at this point you have two options:

1. Reinstall the system using the curernt 2006.1 AMD media.

Advantages:
- you can use the GRP binary packages to do a quick update.
- you avoid recompiling everything for the gcc update
- updating to current should be a fairly small change

Disadvantages:
- You need to be sure to backup your configuration files, or you may
lose something that took a long time to get right.
- If you have/make a lot of changes to USE, you may have a lot of
things that need to be rebuilt after you are "done" with the install.

If you do this, be sure to backup your configuration files, especially
/etc/portage, /etc/make.conf.  Plus you probably want to keep
/var/lib/portage/world as well.

2. Remove ~amd64 from keywords, and basically follow the gcc upgrade
guide, since you probably need to udpate to gcc 4.1 anyway.

Advantages:
- It's relatively easy to see what things are going to be downgraded,
so you can decide what needs to be added to package.keywords.
- Your configuration files will be protected by CONFIG_PROTECT.

Disadvantages:
- You end up doing an emerge -e world, which is going to take quite a
while to execute.


>From a general perspective on running some ~arch packages on an
otherwise stable system, how successful that is usually depends on how
many ~arch packages you have.  ~arch packages tend to depend on other
~arch things, so there is a viral effect that leads some people to
give up and use ~arch for the entire system.  Using the
~cate-gory/package-ver.s.ion syntax can help here, as it only allows
the ~arch keyword for specific versions or -r releases.

HTH,
-Richard
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-09-14  5:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-14  3:33 [gentoo-user] Update or Install again? Testing vs. stable? Alan E. Davis
2006-09-14  5:03 ` Richard Fish [this message]
2006-09-14 13:40   ` Bo Ørsted Andresen
     [not found]     ` <450A3FAF.3070002@qrypto.org>
2006-09-15  7:27       ` Bo Ørsted Andresen
2006-09-15  9:39         ` Rumen Yotov
  -- strict thread matches above, loose matches on Subject: below --
2006-09-14  3:34 Alan E. Davis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7573e9640609132203y30cd0d90m1e7cb1ef6c7265d0@mail.gmail.com \
    --to=bigfish@asmallpond.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox