From: "Andreas Claesson" <andreas.claesson@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] What on Earth is Portage doing for so long?
Date: Fri, 17 Mar 2006 15:49:25 +0100 [thread overview]
Message-ID: <72bdee2f0603170649g2065de0buf7f780d16c919ed2@mail.gmail.com> (raw)
In-Reply-To: <441AC310.7010906@veldy.net>
On 3/17/06, Thomas T. Veldhouse <veldy@veldy.net> wrote:
> Bruno Lustosa wrote:
> > Good question :)
> > But one way to speed this up is to use CDB, so that instead of keeping
> > cache in separate files, it's all in one, resulting in a *much* faster
> > cache update.
> > There are directions here:
> >
> > http://gentoo-wiki.com/TIP_speed_up_portage_with_cdb
> >
> >
> Interesting ... and thanks for the tip. I am concerned about all the
> warnings of breakage though. I need this on my server, which is my
> production firewall at the moment. I would hate to have this fail.
>
A safer way is to update to a newer version of portage.
In portage-2.1 the cache update code is rewritten and it is much faster
then before (but maybe not as fast as CDB).
The biggest reason for the slower update now compared to a year ago,
is that the total number of packages in the tree have increased. The old
code did not handle this very well.
Since this is a server, you probably don't use kde. Excluding all kde split
packages from the portage tree will speed things up a lot.
Create an rsync exclude file and add RSYNC_EXCLUDE="path_to_file" to
your make.conf. Look in man pages for rsync for details.
/Andreas
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-17 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 13:40 [gentoo-user] What on Earth is Portage doing for so long? Thomas T. Veldhouse
2006-03-17 14:02 ` Bruno Lustosa
2006-03-17 14:09 ` Thomas T. Veldhouse
2006-03-17 14:15 ` Alexander Skwar
2006-03-17 20:57 ` Ciaran McCreesh
2006-03-17 22:47 ` Mark Knecht
2006-03-17 14:49 ` Andreas Claesson [this message]
2006-03-17 14:14 ` Daniel da Veiga
2006-03-17 14:28 ` Bo Andresen
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=72bdee2f0603170649g2065de0buf7f780d16c919ed2@mail.gmail.com \
--to=andreas.claesson@gmail.com \
--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