Ned Ludd [EMAIL PROTECTED] posted [EMAIL PROTECTED],
excerpted below, on Wed, 19 Jul 2006 11:10:51 -0400:
On Tue, 2006-07-18 at 17:39 -0400, Mike Frysinger wrote:
On Tuesday 18 July 2006 14:17, Ned Ludd wrote:
There is no consistency for end users when stuff keeps getting shuffled
around.
i dont see why end users should care ... devs should update the
profile/updates/ files and portage should do the rest
Every single year quarter after quarter the more updates
that happen the slower portage is becoming.
Care to solve that?
I don't know all of what portage devs did to fixpackages, but with the
2.1.1-pre series now in ~arch anyway (and I /thought/ in 2.1.0, but I may
have been mistaken), it's /so/ much faster, I finally added
FEATURES=fixpackages to make.conf -- along with the FEATURES=buildpkg I've
had there for some time!
Where back with 2.0.5x, it would take forever, starting with moves even
before I had a Gentoo installed (I never did figure out why it couldn't
start from the date of the last one and only do any new fixes, or at
/least/ ignore ones from before my first Gentoo install), now it seems to
skip over them all at once and only slow down when it gets to new
packages. IOW, it seems like they've implemented the timestamp thing and
only update things since then, like I would have thought reasonable to do
all along.
To put it another way, with new portage, fixpackages doesn't seem to be an
issue at all! My first emerge --pretend --update --deep --newuse world
(before it's all memory cached) seems to take longer than fixpackages
does, now. Either they did something very right, or they did something
very wrong and it's skipping everything it should be doing, therefore
explaining the dramatic speed improvements! =8^)
In any case, I used to dread running fixpackages, but it's now simply not
an issue! =8^)
--
Duncan - List replies preferred. No HTML msgs.
Every nonfree program has a lord, a master --
and if you use the program, he is your master. Richard Stallman
--
gentoo-dev@gentoo.org mailing list
