On Wed, Feb 1, 2012 at 11:19, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> As discussed on IRC, I think some of the code here should really be
> integrated into the bitbake git fetcher to ensure we have a
> clean/consistent API for fetcher functionality. The interface I'm
> thinking about would be similar to SRCPV:
>
> SRCPV = "${@bb.fetch2.get_srcrev(d)}"
>
> with a new fetcher call being added such as get_simplified_srcrev(d).
> Switching between the simplified revision and the description could be
> governed by a variable setting similar to some of the existing variables
> that control fetcher behaviour.
>
I fully agree that having some of the code here ought to be in bitbake git
fetcher but I'd like to work on this after this code has been merge onto
OE-Core mostly because this will blocker on newer bitbake version
requirement and some layers are using it but now depending on meta-oe just
because of this class.
> There has been substantial work done to improve the fetcher APIs and
> clean up the various corner cases and this would seem a logical
> continuation of that, in keeping with the objectives of OE-Core.
Can this be merged and afterwareds I refactor it moving part of this code
onto bitbake? I am not used to bitbake code and I don't have enough time to
learn it in following week or so.
--
Otavio Salvador O.S. Systems
E-mail: ota...@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
