Re: [PATCH 2/9] file: 5.23 -> 5.24

Richard Purdie
2015-07-29T12:52:17Z

On Tue, 2015-07-28 at 15:48 +0200, Martin Jansa wrote:
> On Tue, Jul 28, 2015 at 02:08:20PM +0100, Burton, Ross wrote:
> > On 28 July 2015 at 03:12, Robert Yang <liezhi.yang@windriver.com> wrote:
> >
> > > * Use git repo rather than tarball since the original SRC_URI is not
> > > stable, it is not reachable sometimes.
> > >
> >
> > Personally speaking I see this as a recipe for a release of file which just
> > happens to use git to fetch the tarball (and presumably that hash is the
> > 5.24 tag). In situations like this I prefer to see the recipe called
> > file_5.24.bb as there's no point having a giant PV including git SHAs when
> > it's just the release.
>
> until someone sets SRCREV_pn-file = "${AUTOREV}" somewhere and git SHAs
> in PV suddenly gets very useful.
>
> Personally speaking I prefer recipes with git SCM in SRC_URI named
> <foo>_git.bb and PV set to "A.B.C+gitr${SRCPV}".

Having thought a bit about this, I have to admit I have a preference for
not doing this, just so we can know it is meant to be file 5.24 and not
that version plus some random git commits. If you override SRCREV, you
can override PV too to match the SRCREV.

Perhaps more importantly, its also more useful for the version
comparisons in the update tracking tooling. That might tip the balance.

Cheers,

Richard