All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Barker <pbarker@toganlabs.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [PATCH][meta-raspberrypi] linux-raspberrypi_dev: don't use AUTOREV
Date: Tue, 30 May 2017 18:15:03 +0100	[thread overview]
Message-ID: <CAPyrkgyar=GAr2QkqPe+Tjg=yp=yde_V3MKoXSeKZFb9StCXBw@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1so+EmqtQFL-GbMyEQtpOOevOjRnqHbzXUvs4eb3m04XLw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]

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.

[-- Attachment #2: Type: text/html, Size: 1678 bytes --]

  reply	other threads:[~2017-05-30 17:15 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 [this message]
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
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='CAPyrkgyar=GAr2QkqPe+Tjg=yp=yde_V3MKoXSeKZFb9StCXBw@mail.gmail.com' \
    --to=pbarker@toganlabs.com \
    --cc=raj.khem@gmail.com \
    --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.