About zipping.. Default settings might not really be good idea - i think
that fastest might be even better. Considering that portage tree contains
same word again and again (like applications) it needs pretty small
dictionary to make it much smaller. Decompressing will not be reading from
disc,
On Tue, Dec 2, 2008 at 4:42 AM, Tambet [EMAIL PROTECTED] wrote:
About zipping.. Default settings might not really be good idea - i think
that fastest might be even better. Considering that portage tree contains
same word again and again (like applications) it needs pretty small
dictionary to
It might be that your hard drive is not that much slower than memory, then,
but I really doubt this one ...or it could mean that reading gzip out is
much slower than reading cat - and this one is highly probable. I mean, file
size of gzip.
Actually it's elementary logic that decompressing is
I completely forgot about Google's Summer of Code! Thanks for reminding me.
Hopefully I won't forget again by the time summer rolls around, obviously I
wouldn't mind getting a little extra money for doing something I'd do for
free anyway.
On a more related note: What, exactly, does porttree.py
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Emma Strubell wrote:
I completely forgot about Google's Summer of Code! Thanks for reminding me.
Hopefully I won't forget again by the time summer rolls around, obviously I
wouldn't mind getting a little extra money for doing something I'd do for
Thanks for the clarification. I was planning on forcing an update of the
index as a part of emerge --sync, and implementing a command that would
update the search index (leaving it up to the user to update after making
any manual changes to the portage tree). That way the search index should
I would suggest a different way of updates. When you manually change portage
tree, you have to make an overlay. Overlay, as it's updated and managed by
human being, will be always small (unless someone makes a script, which
creates million overlay updates, but I dont think it would be efficient
Good point. I may just ignore overlays completely because 1) I don't use
them and 2) does anyone really need to search an overlay anyway? aren't any
packages added via an overlay added deliberately?
On Mon, Dec 1, 2008 at 4:52 PM, Tambet [EMAIL PROTECTED] wrote:
I would suggest a different way
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Emma Strubell schrieb:
2) does anyone really need to search an overlay anyway?
Of course. Take large (semi-)official overlays like sunrise. They can
easily be seen as a second portage tree.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9
2008/12/2 Emma Strubell [EMAIL PROTECTED]
True, true. Like I said, I don't really use overlays, so excuse my
igonrance.
Do you know an order of doing things:
Rules of Optimization:
- Rule 1: Don't do it.
- Rule 2 (for experts only): Don't do it yet.
What this actually means -
yes, yes, i know, you're right :]
and thanks a bunch for the outline! about the compression, I agree that it
would be a good idea, but I don't know how to implement it. not that it
would be difficult... I'm guessing there's a gzip module for python that
would make it pretty straightforward? I
11 matches
Mail list logo
