[oe] srctree & gitver

[Chris Larson]

This doesn't answer my question, however.  You wouldn't be able to
safely use AUTOPV in PV unless you're pointing S to an existing
non-fetched git repository, since PV would change before and after the
fetch, so I was attempting to clarify this. Since you can't use it
safely for fetched sources, it doesn't really belong in bb.fetch.

On Tue, Sep 1, 2009 at 3:29 PM, Otavio Salvador<otavio at ossystems.com.br> wrote:
> In bitbake.conf
>
> @@ -532,6 +534,7 @@ UPDATECOMMAND_svn = "/usr/bin/env svn update ${SVNCOOPTS}"
>  SRCDATE = "${DATE}"
>  SRCREV = "1"
>  AUTOREV = "${@bb.fetch.get_srcrev(d)}"
> +AUTOPV = "${@bb.fetch.describe_revision(d)}"
>
>  SRC_URI = "file://${FILE}"
>
> On Tue, Sep 1, 2009 at 1:24 PM, Chris Larson<clarson at kergoth.com> wrote:
>> Seems interesting, but how are you making use of it?  It wouldn't be
>> particularly useful for recipes that have to fetch, since you can't
>> change PV before and after fetch without things exploding.
>>
>> On Tue, Sep 1, 2009 at 6:38 AM, Otavio Salvador<otavio at ossystems.com.br> wrote:
>>> Hello Chris,
>>>
>>> On Wed, Aug 26, 2009 at 11:05 PM, Chris Larson<clarson at kergoth.com> wrote:
>>> [...]
>>>> gitver facilitates extraction of version information from git.  By
>>>> default, it runs 'git describe' to get the version.  If that fails, it
>>>> will set the version to 0.0-<sha1 hash>.  This version is stored in
>>>> the ${GITVER} variable, and can be used in the recipe's PV variable.
>>>> When using this, it will automatically detect changes to .git/HEAD
>>>> (i.e. commit your local changes, check out a different branch, ..) and
>>>> invalidate the bitbake cache, pick up the new PV, and know that it
>>>> needs to re-run the build steps.
>>> [...]
>>>
>>> In the line of your gitver class we've been using a bitbake change for
>>> it already for some time.
>>>
>>> What we did is to add a AUTOPV (as we have AUTOREV) to bitbake and use it in OE.
>>>
>>> I'm attaching the diff for it here.
>>>
>>> --
>>> Otavio Salvador                  O.S. Systems
>>> E-mail: otavio at ossystems.com.br  http://www.ossystems.com.br
>>> Mobile: +55 53 9981-7854         http://projetos.ossystems.com.br
>>>
>>> _______________________________________________
>>> Openembedded-devel mailing list
>>> Openembedded-devel at lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>>
>>>
>>
>>
>>
>> --
>> Chris Larson
>> clarson at kergoth dot com
>> clarson at mvista dot com
>> Founder - BitBake, OpenEmbedded, OpenZaurus
>> Maintainer - Tslib
>> Software Engineer
>> MontaVista Software, Inc.
>>
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel at lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>>
>
>
>
> --
> Otavio Salvador                  O.S. Systems
> E-mail: otavio at ossystems.com.br  http://www.ossystems.com.br
> Mobile: +55 53 9981-7854         http://projetos.ossystems.com.br
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



-- 
Chris Larson
clarson at kergoth dot com
clarson at mvista dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Software Engineer
MontaVista Software, Inc.