From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [V2][PATCH] mesa: Upgrade to 10.4.0
Date: Fri, 30 Jan 2015 09:05:20 +0000 [thread overview]
Message-ID: <1422608720.5312.13.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP71WjwCEkOzO0Xdz0emhSk0j3Fi3o9SH-AbEuP=Jawp7ioQig@mail.gmail.com>
On Fri, 2015-01-30 at 09:02 +0100, Nicolas Dechesne wrote:
> On Fri, Jan 30, 2015 at 8:56 AM, Pengyu Ma <pengyu.ma@windriver.com> wrote:
> > Understood, but there are 2 version mesa_xxx.bb and mesa_git.bb.
> > Is there any reason why keep two versions?
>
> right. this is indeed a good question. I am not sure what the
> 'semantics' of the _git.bb recipe really is. In my minds the _git was
> supposed to point to development branch, or -rc release... looking at
> history it seems we keep it in sync with the other mesa recipe.. so i
> am not actually sure why we do that.. maybe someone else can answer.
There once was a plan to have something closer to upstream for testing
and getting things from the SCM is the way to do that. The indent was to
learn about issues before they got released rather than afterwards.
As such, we have pieces of this around, the poky-bleeding DISTRO setting
for example was meant to enable the git versions of recipes.
Some people when developing/testing/debugging have developed git
versions of recipes and where they still work and aren't a maintenance
burden, we've left them. I've personally used a few recipes like that
and I know others have too.
I do still dream of the day we'll have the resources/technology to make
poky-bleeding a reality again.
So the git recipe is intended to look beyond the last stable release or
otherwise be the same.
Cheers,
Richard
next prev parent reply other threads:[~2015-01-30 9:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 8:57 [V2][PATCH] mesa: Upgrade to 10.4.0 Pengyu Ma
2015-01-29 9:53 ` Nicolas Dechesne
2015-01-29 10:05 ` Pengyu Ma
2015-01-29 10:10 ` Nicolas Dechesne
2015-01-29 10:35 ` Burton, Ross
2015-01-30 1:51 ` Pengyu Ma
2015-01-30 7:51 ` Nicolas Dechesne
2015-01-30 7:56 ` Pengyu Ma
2015-01-30 8:02 ` Nicolas Dechesne
2015-01-30 9:05 ` Richard Purdie [this message]
2015-01-30 9:12 ` Pengyu Ma
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=1422608720.5312.13.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=nicolas.dechesne@linaro.org \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox