From: Khem Raj <raj.khem@gmail.com>
To: Andrei Gherzan <andrei@gherzan.ro>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV
Date: Wed, 31 May 2017 17:17:17 -0700 [thread overview]
Message-ID: <CAMKF1sqVEbdMKnqHHwsdWrs6aPDOowreRCZuk2h39J2XQEV8TA@mail.gmail.com> (raw)
In-Reply-To: <CAK18fxF3uXOdsZkaN9f-DKJaMc+4GVfW28xTVK9a-01x+ktLXA@mail.gmail.com>
On Wed, May 31, 2017 at 5:00 PM, Andrei Gherzan <andrei@gherzan.ro> wrote:
>
> On Tue, May 30, 2017 at 6:29 PM, Khem Raj <raj.khem@gmail.com> wrote:
>>
>> On Tue, May 30, 2017 at 10:25 AM, Andre McCurdy <armccurdy@gmail.com>
>> wrote:
>> > On Tue, May 30, 2017 at 10:15 AM, Paul Barker <pbarker@toganlabs.com>
>> > wrote:
>> >> On 30 May 2017 5:08 p.m., "Khem Raj" <raj.khem@gmail.com> wrote:
>> >>
>> >> On Tue, May 30, 2017 at 12:57 AM, Martin Jansa <martin.jansa@gmail.com>
>> >> wrote:
>> >>> * use latest revision in rpi-4.11.y branch
>> >>> * using AUTOREV causes bitbake to run git ls-remote on the github.com
>> >>> repository in order
>> >>> to convert AUTOREV to currently latest SRCREV even when you don't
>> >>> use
>> >>> linux-raspberrypi_dev
>> >>> at all, just happen to have meta-raspberrypi layer in your
>> >>> bblayers.conf, that's bad for
>> >>> people who want to be able to build without network access
>> >>> (completely
>> >>> from premirror)
>> >>>
>> >>
>> >> These branches get rebased often so locking SRCREV caused another
>> >> kind of problem. what we can do is.
>> >>
>> >> 1. Let user like you override the SRCREC via a bbappend or conf file.
>> >> so change the assignment to ?=
>> >> 2. Delete the recipe completely. We lose some of upstream testing.
>> >>
>> >> We should be able to skip the recipe if it isn't selected as the
>> >> preferred
>> >> version and/or provider of "virtual/kernel". I'm out at the minute so
>> >> can't
>> >> look at it now but will try to take a look later this week.
>> >
>> > The linux-yocto-dev.bb recipe contains an example of doing that.
>> >
>>
>> ah perfect. Thats what we need here
>>
>>
>> http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-kernel/linux/linux-yocto-dev.bb?h=master#n28
>>
>> please rename the recipe to be linux-raspberrypi-dev.bb and add the magic
>> above and send a v2
>>
>
> Using the magic above we still hardcode a revision there. So if a user wants
> to compile the recipe without setting the preferred provider it will fail.
what will be the usecase ? when you have a different kernel selected but
woould like to compile yet another kernel
that rev can be a well known rev like branchpoint. Moreover, I think
if someone wants to use the dev recipe then its expected that they
switch
to using AUTOREV or some other local mechanism for pinning if needed.
>
> --
> Andrei Gherzan
next prev parent reply other threads:[~2017-06-01 0:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 7:57 [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV Martin Jansa
2017-05-30 16:07 ` Khem Raj
2017-05-30 17:15 ` Paul Barker
2017-05-30 17:25 ` Andre McCurdy
2017-05-30 17:29 ` Khem Raj
2017-06-01 0:00 ` Andrei Gherzan
2017-06-01 0:17 ` Khem Raj [this message]
2017-06-01 6:10 ` Paul Barker
2017-06-01 7:08 ` Martin Jansa
2017-06-01 7:10 ` Martin Jansa
2017-06-01 11:23 ` Paul Barker
2017-06-01 12:48 ` Andrei Gherzan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMKF1sqVEbdMKnqHHwsdWrs6aPDOowreRCZuk2h39J2XQEV8TA@mail.gmail.com \
--to=raj.khem@gmail.com \
--cc=andrei@gherzan.ro \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.