On Mon, 2016-05-23 at 16:36 +0300, Alexander Kanavin wrote:
> On 05/23/2016 04:10 PM, Richard Purdie wrote:
> > > > -SRCREV = "ebc330eac8b9d38e9aef9f01e7241c904bd01073"
> > > > +SRCREV = "69d03e2aceb79cf7a616c07f8e0be4e1f9f7976b"
> > > > PV = "0.0+git${SRCPV}"
> > >
> > > This is a good moment to start using git version tags instead of
> > > just
> > > updating commit ids.
> > >
> > > Let's bring down the amount of 'unknown' upstream versions to
> > > zero or
> > > close to it:
> > >
> > > http://recipes.yoctoproject.org/rrs/recipes/2.2/M1/?upstream_stat
> > > us=U
> > > nknown#
> >
> > Sadly, "tags" need a network to resolve them and hence using them
> > means
> > the metadata doesn't work standalone. We can't do that.
>
> I need to clarify: I would like the version number in PV to match an
> existing upstream version tag. So that the upstream version check
> works
> correctly.
>
> The actual git revision for builds will continue to be determined by
> commit ids in SRCREV.
That does indeed make sense. I'd be happy to see some release tarballs
for some of these things and some upstream version tags...
Cheers,
Richard
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
