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: Kent Fredric <kentfredric@...>
Subject: Re: comprehensive eclass checking in repoman
Date: Fri, 25 May 2012 08:52:25 +1200
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.

And considering how fast eclasses change, I doubt you'd need to
regenerate it often. Though how much time it takes to parse and stuff
really needs to be properly benched, its more that there is an
intermediate state that can be inspected by human eyes instead of a
lot of magic going on



-- 
Kent

perl -e  "print substr( \"edrgmaM  SPA NOcomil.ic\\@tfrken\", \$_ * 3,
3 ) for ( 9,8,0,7,1,6,5,4,3,2 );"

http://kent-fredric.fox.geek.nz


Replies:
Re: comprehensive eclass checking in repoman
-- Zac Medico
References:
comprehensive eclass checking in repoman
-- Mike Frysinger
Re: comprehensive eclass checking in repoman
-- Kent Fredric
Re: comprehensive eclass checking in repoman
-- Zac Medico
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: comprehensive eclass checking in repoman


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.