From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] digest-* files in portage tree
Date: Fri, 25 Mar 2005 02:46:05 +0100 [thread overview]
Message-ID: <20050325024605.0154e89a@sven.genone.homeip.net> (raw)
In-Reply-To: <20050324154205.GB32460@olive.flatmonk.org>
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
On Thu, 24 Mar 2005 10:42:05 -0500
Aron Griffis <agriffis@gentoo.org> wrote:
> Francesco Riosa wrote: [Thu Mar 24 2005, 08:22:40AM EST]
> > In addition to "Manifest" files in portage tree there are 19000
> > "digest-${P}" files in the portage tree each of this uses 4k on
> > ext{2,3} filesystem and has to be scanned each time rsync is run on
> > the tree. Is possible to avoid the use of theese files?
>
> A few mods to portage and it should be possible to give the Manifest
> a structure to contain the digests...
Yeah, I might reconsider my digest-redesign I sent here a few months ago
if there is actually interest in this.
Marius
--
Public Key at http://www.genone.de/info/gpg-key.pub
In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-03-25 1:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 13:22 [gentoo-dev] digest-* files in portage tree Francesco Riosa
2005-03-24 13:36 ` Chris Gianelloni
2005-03-24 14:16 ` Francesco Riosa
2005-03-24 14:37 ` Mike Frysinger
2005-03-24 15:45 ` Francesco Riosa
2005-03-24 15:42 ` Aron Griffis
2005-03-25 1:46 ` Marius Mauch [this message]
2005-03-25 4:28 ` Daniel
2005-03-27 3:31 ` Daniel
2005-03-26 7:43 ` Peter Cech
2005-03-25 6:04 ` Daniel Goller
2005-03-25 7:12 ` Robin H. Johnson
2005-03-25 23:55 ` [gentoo-dev] " Duncan
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=20050325024605.0154e89a@sven.genone.homeip.net \
--to=genone@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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