From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] metadata/md5-cache
Date: Sat, 02 Jun 2012 23:41:54 -0700 [thread overview]
Message-ID: <4FCB0732.3040208@gentoo.org> (raw)
In-Reply-To: <m3zk8l9hmt.fsf@carbon.jhcloos.org>
On 06/02/2012 08:52 PM, James Cloos wrote:
>>>>>> "ZM" == Zac Medico <zmedico@gentoo.org> writes:
>
> Thanks for the quick reply and the reference to the bz.
>
> ZM> We had a bug about that [1] when we first deployed md5-cache, but it's
> ZM> supposed to have been fixed.
>
> It is not fixed. The behavior has not changed in any way since md5-cache was added.
As I've noted on the bug, a simple mtime check on the cache entries
seems to indicate that it's working properly.
> ZM> [1] https://bugs.gentoo.org/show_bug.cgi?id=410505
>
> I've added a please re-open note to that bug.
>
> Thanks for working on it.
One way that we can reduce the amount of cache regeneration is to add
support for elibs:
http://www.gentoo.org/proj/en/glep/glep-0033.htm
Since elibs aren't allowed to modify the ebuild metadata, the metadata
cache doesn't need to be regenerated when elibs are modified. For
example, if eutils was an elib, we would avoid a lot of cache
regeneration each time it was modified.
--
Thanks,
Zac
next prev parent reply other threads:[~2012-06-03 9:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 0:32 [gentoo-dev] metadata/md5-cache James Cloos
2012-06-03 0:54 ` Zac Medico
2012-06-03 3:52 ` James Cloos
2012-06-03 6:41 ` Zac Medico [this message]
2012-06-03 7:22 ` Michał Górny
2012-06-03 8:31 ` [gentoo-dev] metadata/md5-cache Duncan
2012-06-03 9:25 ` Robin H. Johnson
2012-06-03 9:34 ` Michał Górny
2012-06-03 9:48 ` Robin H. Johnson
2012-06-04 7:27 ` Michał Górny
2012-06-04 13:15 ` Brian Harring
2012-06-04 23:56 ` Brian Harring
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=4FCB0732.3040208@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-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