public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Philippe Lafoucrière" <lafou@wanadoo.fr>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Re: Re: portage-ng roadmap?
Date: Fri, 16 Jul 2004 09:14:55 +0200	[thread overview]
Message-ID: <40F7806F.4000200@wanadoo.fr> (raw)
In-Reply-To: <42170.202.117.114.8.1089898236.squirrel@202.117.114.8>

>>need help ?
>>I'd like to work on the cache part, since I'm getting sic of "emerge rsync".
> 
> 
> A big change in what I have, which is not nearly workeable yet (and I won't
> work on it at all until august) is that it tries to use lazy evaluation
> techniques combined with in memory caching. When you open an ebuild object you
> can do with it whatever you want but the actual file is only read at the
> moment you request the value of a property other than the version. Similarly
> the packages in a category are only requested on demand. Searching (emerge -s
> like) uses a smart strategy using the glob function ;-). The cache
> precalculation should not be necessary for the full rewrite.


Paul,

do you think end-users need all ebuilds ? I have a laptop, and fetching 
the whole portage tree doesn't make any sence, since I emerge only a few 
apps. On the other hand, I'd like to fetch a "pre-computed" cache or 
world file, and fetch only ebuilds when necessary (emerging a package 
for example). Those "emerge rsync" are way too long, and can be 
drasticly reducted using a different way of thinking.

Of course, the whole portage tree could be installed, as it is in FreeBSD ;)

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


  reply	other threads:[~2004-07-16  7:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-28  8:44 [gentoo-portage-dev] portage-ng roadmap? Adrian Gschwend
2004-06-28 14:08 ` Marius Mauch
2004-06-28 22:55   ` Roman Gaufman
2004-06-29  7:52   ` [gentoo-portage-dev] " Adrian Gschwend
2004-06-29 18:44     ` Hasan Khalil
2004-06-29 21:15       ` George Shapovalov
2004-06-30  9:03         ` [gentoo-portage-dev] " Adrian Gschwend
2004-06-30  9:07           ` John Nilsson
2004-06-30  9:24             ` [gentoo-portage-dev] " Adrian Gschwend
2004-06-30 20:07           ` [gentoo-portage-dev] " Paul de Vrieze
2004-06-30 21:41             ` Brian Harring
2004-06-30 22:23               ` Nathaniel McCallum
2004-07-01  9:25                 ` Paul de Vrieze
2004-07-12  9:08             ` Philippe Lafoucrière
2004-07-12  9:17               ` Michael Kohl
2004-07-12 10:44                 ` Brian Harring
2004-07-15 13:30               ` Paul de Vrieze
2004-07-16  7:14                 ` Philippe Lafoucrière [this message]
2004-07-16  8:10                   ` Paul de Vrieze
2004-07-16  8:49                     ` Philippe Lafoucrière
2004-07-04 21:35           ` Pieter Van den Abeele
2004-07-05 11:05             ` [gentoo-portage-dev] " Adrian Gschwend
2004-07-05 21:24               ` Pieter Van den Abeele
2004-07-07 20:54             ` [gentoo-portage-dev] " gentoo
2004-07-07 19:49               ` [gentoo-portage-dev] unsubscribing (was: Re: portage-ng roadmap?) Andrew Gaffney
2004-06-30  9:03       ` [gentoo-portage-dev] Re: Re: portage-ng roadmap? Adrian Gschwend
2004-06-30 13:06         ` Hasan Khalil
2004-07-04 21:45   ` [gentoo-portage-dev] " Pieter Van den Abeele
  -- strict thread matches above, loose matches on Subject: below --
2004-07-16 10:04 [gentoo-portage-dev] Re: " Paul de Vrieze

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=40F7806F.4000200@wanadoo.fr \
    --to=lafou@wanadoo.fr \
    --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