public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Barry.SCHWARTZ@chemoelectric.org
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64]  Re: Upgrading from amd64 to ~amd64.
Date: Tue, 18 Oct 2005 15:25:51 -0500	[thread overview]
Message-ID: <20051018202551.GA12823@crud.crud.mn.org> (raw)
In-Reply-To: <pan.2005.10.18.11.09.37.15688@cox.net>

[-- Attachment #1: Type: text/plain, Size: 1243 bytes --]

Duncan <1i5t5.duncan@cox.net> skribis:
> I /always/ do an emerge --pretend --update --deep world run first,

I use 'emerge -1NuDv world -p' then strip the '-p' if I wish to
proceed. I have buildpkg in my features, as well as portage logging.

But for a full upgrade to ~amd64 I would add -e and --tree to the
flags, to let me see more clearly how packages are being selected, and
to let me prune branches via USE flags.

These days I run ~amd64 by default, but with the glibc from amd64. I
found cups and the whole apache-php-subversion thing difficult to
manage as ~amd64 so I also use the amd64 version there.

I started as amd64 but when I went to ~amd64 I did all the emerging
manually, mainly because I was unfamiliar with what to expect from
'deep' merging, that far back. It was tedious, the way I did it, which
was basically to make a list of packages and check them off. Now I
would probably examine the tree listing check off branches at a time.



-- 
Barry.SCHWARTZ@chemoelectric.org   http://www.chemoelectric.org
Esperantistoj rajtas skribi al Barijo.SXVARCO@chemoelectric.org
   'And now we're going to go try to comfort people in that
 part of the world.' -- Bush, referring to the southeastern U.S.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-10-18 20:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-18  2:50 [gentoo-amd64] Upgrading from amd64 to ~amd64 Toby Fisher
2005-10-18  3:09 ` Barry.SCHWARTZ
2005-10-18  3:15 ` Mark Knecht
2005-10-18  3:55 ` Richard Freeman
2005-10-18 11:09   ` [gentoo-amd64] " Duncan
2005-10-18 15:58     ` Scott Stoddard
2005-10-19 15:25       ` [gentoo-amd64] " Duncan
2005-10-18 20:25     ` Barry.SCHWARTZ [this message]
2005-10-19 15:35       ` Duncan
2005-10-19 16:06         ` Barry.SCHWARTZ
2005-10-18 20:29     ` [gentoo-amd64] " Barry.SCHWARTZ
2005-10-18 15:28 ` [gentoo-amd64] " Peter Humphrey

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=20051018202551.GA12823@crud.crud.mn.org \
    --to=barry.schwartz@chemoelectric.org \
    --cc=gentoo-amd64@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