[yocto] [meta-raspberrypi][PATCH 1/6] linux-raspberrypi: Allow override of PV

[Khem Raj]

On May 30, 2016 3:15 PM, "Paul Barker" <paul at paulbarker.me.uk> wrote:
>
> On Mon, 30 May 2016 20:58:53 +0300
> Khem Raj <raj.khem at gmail.com> wrote:
>
> > On May 30, 2016 1:09 AM, "Paul Barker" <paul at paulbarker.me.uk> wrote:
> > >
> > > On Sun, 29 May 2016 21:20:21 +0300
> > > Khem Raj <raj.khem at gmail.com> wrote:
> > >
> > > > On May 29, 2016 9:00 AM, "Paul Barker" <paul at paulbarker.me.uk>
> > > > wrote:
> > > > >
> > > > > PV is now set in each version of the linux-raspberrypi recipe
> > > > > instead of
> > > > in
> > > > > linux-raspberrypi.inc. This allows linux-raspberrypi.inc to be
> > > > > used in
> > > > custom
> > > > > kernel recipes in another layer which require a different PV
> > > > > value.
> > > >
> > > > You  can also use weak define. Instead of duplicated value in each
> > > > recipe
> > >
> > > Weak define doesn't work here as PV is already weakly defined based
> > > on the recipe filename and that's what we're trying to override. We
> > > end up with PV values like "4.1" instead of "4.1.21+git..." if "?="
> > > is used.
> >
> > What issue do we have if we ask custom recipes to define LINUX_VERSION
>
> I'm trying to build from a source archive instead of a git repository
> (to avoid a ~1.3GB git clone operation) so the use of ${SRCPV} is
> causing me trouble.
>

Can you override the whole PV
> Thanks,
> Paul Barker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20160531/a0d5f2d6/attachment.html>