Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Zac Medico <zmedico@g.o>
Subject: Re: comprehensive eclass checking in repoman
Date: Thu, 24 May 2012 14:00:25 -0700
On 05/24/2012 01:52 PM, Kent Fredric wrote:
> On 25 May 2012 08:28, Zac Medico <zmedico@g.o> wrote:
>>
>> I expect that reading and validating the cache is probably not going to
>> be much faster than just parsing the eclasses over again.
>> --
> 
> Unless, you don't care if the cache is out-dated because the cache is
> optional / the syntax checking is optional, and its only made
> available when you generate it manually.

Putting the responsibility of cache validation on the user is not really
an option here, because it's just going to lead to bug reports of the
form "repoman is using stale eclass info in its checks".
-- 
Thanks,
Zac


References:
comprehensive eclass checking in repoman
-- Mike Frysinger
Re: comprehensive eclass checking in repoman
-- Kent Fredric
Re: comprehensive eclass checking in repoman
-- Zac Medico
Re: comprehensive eclass checking in repoman
-- Kent Fredric
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: comprehensive eclass checking in repoman
Next by thread:
Re: comprehensive eclass checking in repoman
Previous by date:
Re: comprehensive eclass checking in repoman
Next by date:
Re: Portage Git migration - Handling Pull Requests (Was: clean cut or git-cvsserver)


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.