Gentoo Archives: gentoo-amd64

From: Barry.SCHWARTZ@×××××××××××××.org
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] Re: Upgrading from amd64 to ~amd64.
Date: Tue, 18 Oct 2005 20:28:41
Message-Id: 20051018202551.GA12823@crud.crud.mn.org
In Reply to: [gentoo-amd64] Re: Upgrading from amd64 to ~amd64. by Duncan <1i5t5.duncan@cox.net>
1 Duncan <1i5t5.duncan@×××.net> skribis:
2 > I /always/ do an emerge --pretend --update --deep world run first,
3
4 I use 'emerge -1NuDv world -p' then strip the '-p' if I wish to
5 proceed. I have buildpkg in my features, as well as portage logging.
6
7 But for a full upgrade to ~amd64 I would add -e and --tree to the
8 flags, to let me see more clearly how packages are being selected, and
9 to let me prune branches via USE flags.
10
11 These days I run ~amd64 by default, but with the glibc from amd64. I
12 found cups and the whole apache-php-subversion thing difficult to
13 manage as ~amd64 so I also use the amd64 version there.
14
15 I started as amd64 but when I went to ~amd64 I did all the emerging
16 manually, mainly because I was unfamiliar with what to expect from
17 'deep' merging, that far back. It was tedious, the way I did it, which
18 was basically to make a list of packages and check them off. Now I
19 would probably examine the tree listing check off branches at a time.
20
21
22
23 --
24 Barry.SCHWARTZ@×××××××××××××.org http://www.chemoelectric.org
25 Esperantistoj rajtas skribi al Barijo.SXVARCO@×××××××××××××.org
26 'And now we're going to go try to comfort people in that
27 part of the world.' -- Bush, referring to the southeastern U.S.

Replies

Subject Author
[gentoo-amd64] Re: Re: Upgrading from amd64 to ~amd64. Duncan <1i5t5.duncan@×××.net>