From: "Jesús Guerrero" <i92guboj@terra.es>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Upgrade
Date: Tue, 11 Sep 2007 15:50:07 +0200 [thread overview]
Message-ID: <20070911155007.0521c69d.i92guboj@terra.es> (raw)
In-Reply-To: <46E697D9.8030105@alice.it>
On Tue, 11 Sep 2007 15:27:53 +0200
econti <contiemilio@alice.it> wrote:
> Hi everybody, this is my first post on the list.
>
> Well, I'm running a 2.6.15-gentoo-r7 2006.0 on a AMD64 machine.
>
> Now I'd like to make a world upgrade. I know that I should run the
> following commands:
>
> emerge --sync
> emerge --update --deep --newuse world
> emerge --depclean
> revdep-rebuild
>
> A little question: how long does it take to complete the upgrade?
> (sure, it depends on the installed software, but please give me an
> approximation)
>
It's impossible, since it doesn't only depends on the installed
software. It also depends on many other factors:
1.- the time when you did the last update
2.- the number of packages that has updates, which is not always
related to the number of packages you have installed, but to
_what_ packages do you have installed. Some packages doesn't
get updates too frequently, while others change a lot.
3.- external factors, like overlays
It just depends on _what_ needs to be updated.
I can give you a few hints, though. Most packages can compile in
a reasonable amount of time. Some specific packages will take
longer to compile. You will learn to identify them with the time.
For example, openoffice if probably the largest, and can take from
several hours up to days, depending on your hardware. Some kde
packages are big, like kmail. Qt or Gtk as intermediate things.
Glibc and gcc can take a lot of time, as xorg-server, for example.
Whe you are doing the update, you have to know a few things. On first
place, use this instead of your command above:
merge --update --deep --newuse --verbose --ask world
This will present you with a list of the packages that will be
updated, that way, you know how many packages are going to be
updated, but, more important, you will know _what_ packages will
be merged.
The depclean and revdep steps shouldn't be too time consuming
on a sane system. So, if you use them regularly, those steps
will not rob much of your time. The sync step depends on your
connection speed and the time since your last sync. It can take
a few minutes on a fast connection if your tree is up to date.
But it can take a day on a 56k modem if you tree is empty or
way too outdated.
--
Jesús Guerrero <i92guboj@terra.es>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2007-09-11 14:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 13:27 [gentoo-user] Upgrade econti
2007-09-11 13:34 ` Alexander Reitzel
2007-09-11 13:50 ` Jesús Guerrero [this message]
2007-09-11 13:59 ` Dale
2007-09-11 14:09 ` Alan McKinnon
2007-09-11 14:19 ` Rodrigo Forlin
2007-09-11 14:28 ` Denis
2007-09-11 14:50 ` David
2007-09-11 18:54 ` econti
2007-09-11 14:40 ` Neil Bothwick
2007-09-11 14:53 ` Gary Rickert
2007-09-11 15:05 ` Bo Ørsted Andresen
2007-09-14 15:21 ` econti
2007-09-14 21:42 ` Neil Bothwick
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=20070911155007.0521c69d.i92guboj@terra.es \
--to=i92guboj@terra.es \
--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