public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joseph Booker" <joe@neoturbine.net>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] portage doc & cache
Date: Sat, 12 Jun 2004 17:25:54 -0500 (CDT)	[thread overview]
Message-ID: <33656.68.78.45.223.1087079154.squirrel@webmail.neoturbine.net> (raw)
In-Reply-To: <40CAC668.6020100@wanadoo.fr>


Philippe Lafoucrière said:
> That's the idea. If you look at debian package system (I know, it's far
> different, but ideas can be used on both projects), an update will
> only fetch the "cache", and then, package en demand (using apt-get
> install)

For someone like me using mysql-based cache rather then portage's default
cache, how will that figure?

> There are too many files to consider now in portage. At start, portage
> had just a few hundred of files, and rsync was doing its job quite well.
> Now portage has more than 80 000 files. Rsync has to consider all of
> them, and it's *REALLY* too long + painfull (my laptop is almost
> unusable during rsyncing). Sound like a "select * from table" on a test
> server with 15 test clients => will break in production environnement
> with thousands of clients.

I have a 900mhz celeron (copermine), and maybe its the love-sources and
~x86 packages, but ive still been able to do crazy things like talk on
irc, have firefox open, update some programs, all while 'emerge sync'-ing
without too much preformance lost* (now if i forget to turn off
seti@home.....then my computer will simply lockup untill i can get to a
tty). You might want to check out if theres something with your laptop, if
these extremly long times happen with other equpiment.

* I should mention i emerge sync every one or two days.
-- 
 Joe Booker

--
gentoo-portage-dev@gentoo.org mailing list


  reply	other threads:[~2004-06-12 22:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-11 21:15 [gentoo-portage-dev] portage doc & cache Philippe Lafoucrière
2004-06-11 23:06 ` Nicholas Jones
2004-06-12  0:55 ` John Nilsson
2004-06-12  9:01   ` Philippe Lafoucrière
2004-06-12 22:25     ` Joseph Booker [this message]
2004-06-13  9:45       ` Philippe Lafoucrière
2004-06-13 15:41         ` Nicholas Jones
2004-06-13 18:39           ` Philippe Lafoucrière
2004-06-13 16:17         ` Hasan Khalil
2004-06-13 16:24           ` Joseph Booker
2004-06-13 16:46           ` Jeff Smelser
2004-06-13 22:45             ` John Nilsson
2004-06-20 18:54               ` Philippe Lafoucrière
2004-06-12  9:10 ` Philippe Lafoucrière
     [not found]   ` <1087033087.16266.8.camel@newkid.milsson.nu>
2004-06-13  9:35     ` Philippe Lafoucrière

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=33656.68.78.45.223.1087079154.squirrel@webmail.neoturbine.net \
    --to=joe@neoturbine.net \
    --cc=gentoo-portage-dev@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