* [V2][PATCH] mesa: Upgrade to 10.4.0
@ 2015-01-28 8:57 Pengyu Ma
2015-01-29 9:53 ` Nicolas Dechesne
0 siblings, 1 reply; 11+ messages in thread
From: Pengyu Ma @ 2015-01-28 8:57 UTC (permalink / raw)
To: pengyu.ma, openembedded-core
Signed-off-by: Pengyu Ma <pengyu.ma@windriver.com>
---
.../mesa/{mesa-gl_10.3.4.bb => mesa-gl_10.4.0.bb} | 0
.../mesa/{mesa_10.3.4.bb => mesa_10.4.0.bb} | 4 ++--
meta/recipes-graphics/mesa/mesa_git.bb | 4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
rename meta/recipes-graphics/mesa/{mesa-gl_10.3.4.bb => mesa-gl_10.4.0.bb} (100%)
rename meta/recipes-graphics/mesa/{mesa_10.3.4.bb => mesa_10.4.0.bb} (78%)
diff --git a/meta/recipes-graphics/mesa/mesa-gl_10.3.4.bb b/meta/recipes-graphics/mesa/mesa-gl_10.4.0.bb
similarity index 100%
rename from meta/recipes-graphics/mesa/mesa-gl_10.3.4.bb
rename to meta/recipes-graphics/mesa/mesa-gl_10.4.0.bb
diff --git a/meta/recipes-graphics/mesa/mesa_10.3.4.bb b/meta/recipes-graphics/mesa/mesa_10.4.0.bb
similarity index 78%
rename from meta/recipes-graphics/mesa/mesa_10.3.4.bb
rename to meta/recipes-graphics/mesa/mesa_10.4.0.bb
index 50092c9..7d3723e 100644
--- a/meta/recipes-graphics/mesa/mesa_10.3.4.bb
+++ b/meta/recipes-graphics/mesa/mesa_10.4.0.bb
@@ -2,8 +2,8 @@ require ${BPN}.inc
SRC_URI = "ftp://ftp.freedesktop.org/pub/mesa/${PV}/MesaLib-${PV}.tar.bz2"
-SRC_URI[md5sum] = "fa0558a3d02c2bb8c208c030ccdc992e"
-SRC_URI[sha256sum] = "e6373913142338d10515daf619d659433bfd2989988198930c13b0945a15e98a"
+SRC_URI[md5sum] = "b7b37117eecbdfaaf3075acfb063d5a3"
+SRC_URI[sha256sum] = "98a7dff3a1a6708c79789de8b9a05d8042e867067f70e8f30387c15026233219"
S = "${WORKDIR}/Mesa-${PV}"
diff --git a/meta/recipes-graphics/mesa/mesa_git.bb b/meta/recipes-graphics/mesa/mesa_git.bb
index b046ae2..e554ff4 100644
--- a/meta/recipes-graphics/mesa/mesa_git.bb
+++ b/meta/recipes-graphics/mesa/mesa_git.bb
@@ -4,8 +4,8 @@ DEFAULT_PREFERENCE = "-1"
LIC_FILES_CHKSUM = "file://docs/license.html;md5=6a23445982a7a972ac198e93cc1cb3de"
-SRCREV = "c7b9a2e38a3e471562b50dab8be65db8ac6819f8"
-PV = "10.3.4+git${SRCPV}"
+SRCREV = "f70e4d4afd16e66506ce3b055edb3b71b1464890"
+PV = "10.4.3+git${SRCPV}"
SRC_URI = "git://anongit.freedesktop.org/git/mesa/mesa;branch=10.4"
--
1.7.9.5
^ permalink raw reply related [flat|nested] 11+ messages in thread* Re: [V2][PATCH] mesa: Upgrade to 10.4.0
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
0 siblings, 1 reply; 11+ messages in thread
From: Nicolas Dechesne @ 2015-01-29 9:53 UTC (permalink / raw)
To: Pengyu Ma; +Cc: Patches and discussions about the oe-core layer
On Wed, Jan 28, 2015 at 9:57 AM, Pengyu Ma <pengyu.ma@windriver.com> wrote:
>
> diff --git a/meta/recipes-graphics/mesa/mesa-gl_10.3.4.bb b/meta/recipes-graphics/mesa/mesa-gl_10.4.0.bb
> similarity index 100%
> rename from meta/recipes-graphics/mesa/mesa-gl_10.3.4.bb
> rename to meta/recipes-graphics/mesa/mesa-gl_10.4.0.bb
> diff --git a/meta/recipes-graphics/mesa/mesa_10.3.4.bb b/meta/recipes-graphics/mesa/mesa_10.4.0.bb
> similarity index 78%
> rename from meta/recipes-graphics/mesa/mesa_10.3.4.bb
> rename to meta/recipes-graphics/mesa/mesa_10.4.0.bb
why not 10.4.3 directly, instead?
> index 50092c9..7d3723e 100644
> --- a/meta/recipes-graphics/mesa/mesa_10.3.4.bb
> +++ b/meta/recipes-graphics/mesa/mesa_10.4.0.bb
> @@ -2,8 +2,8 @@ require ${BPN}.inc
>
> SRC_URI = "ftp://ftp.freedesktop.org/pub/mesa/${PV}/MesaLib-${PV}.tar.bz2"
>
> -SRC_URI[md5sum] = "fa0558a3d02c2bb8c208c030ccdc992e"
> -SRC_URI[sha256sum] = "e6373913142338d10515daf619d659433bfd2989988198930c13b0945a15e98a"
> +SRC_URI[md5sum] = "b7b37117eecbdfaaf3075acfb063d5a3"
> +SRC_URI[sha256sum] = "98a7dff3a1a6708c79789de8b9a05d8042e867067f70e8f30387c15026233219"
>
> S = "${WORKDIR}/Mesa-${PV}"
>
> diff --git a/meta/recipes-graphics/mesa/mesa_git.bb b/meta/recipes-graphics/mesa/mesa_git.bb
> index b046ae2..e554ff4 100644
> --- a/meta/recipes-graphics/mesa/mesa_git.bb
> +++ b/meta/recipes-graphics/mesa/mesa_git.bb
> @@ -4,8 +4,8 @@ DEFAULT_PREFERENCE = "-1"
>
> LIC_FILES_CHKSUM = "file://docs/license.html;md5=6a23445982a7a972ac198e93cc1cb3de"
>
> -SRCREV = "c7b9a2e38a3e471562b50dab8be65db8ac6819f8"
> -PV = "10.3.4+git${SRCPV}"
> +SRCREV = "f70e4d4afd16e66506ce3b055edb3b71b1464890"
> +PV = "10.4.3+git${SRCPV}"
that's the commit for 10.4.3 tag, this isn't consistent with the
change you did in the non _git recipe.
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [V2][PATCH] mesa: Upgrade to 10.4.0
2015-01-29 9:53 ` Nicolas Dechesne
@ 2015-01-29 10:05 ` Pengyu Ma
2015-01-29 10:10 ` Nicolas Dechesne
0 siblings, 1 reply; 11+ messages in thread
From: Pengyu Ma @ 2015-01-29 10:05 UTC (permalink / raw)
To: Nicolas Dechesne; +Cc: Patches and discussions about the oe-core layer
On 01/29/2015 05:53 PM, Nicolas Dechesne wrote:
> On Wed, Jan 28, 2015 at 9:57 AM, Pengyu Ma <pengyu.ma@windriver.com> wrote:
>> diff --git a/meta/recipes-graphics/mesa/mesa-gl_10.3.4.bb b/meta/recipes-graphics/mesa/mesa-gl_10.4.0.bb
>> similarity index 100%
>> rename from meta/recipes-graphics/mesa/mesa-gl_10.3.4.bb
>> rename to meta/recipes-graphics/mesa/mesa-gl_10.4.0.bb
>> diff --git a/meta/recipes-graphics/mesa/mesa_10.3.4.bb b/meta/recipes-graphics/mesa/mesa_10.4.0.bb
>> similarity index 78%
>> rename from meta/recipes-graphics/mesa/mesa_10.3.4.bb
>> rename to meta/recipes-graphics/mesa/mesa_10.4.0.bb
> why not 10.4.3 directly, instead?
10.4.0 is intel graphic stack 2014 Q4 Release version
https://01.org/linuxgraphics/downloads/2014/2014q4-intel-graphics-stack-release
It is stable and verified with other packages libdrm xorg-video-intel
and xserver-xorg in oe-core master.
>
>
>> index 50092c9..7d3723e 100644
>> --- a/meta/recipes-graphics/mesa/mesa_10.3.4.bb
>> +++ b/meta/recipes-graphics/mesa/mesa_10.4.0.bb
>> @@ -2,8 +2,8 @@ require ${BPN}.inc
>>
>> SRC_URI = "ftp://ftp.freedesktop.org/pub/mesa/${PV}/MesaLib-${PV}.tar.bz2"
>>
>> -SRC_URI[md5sum] = "fa0558a3d02c2bb8c208c030ccdc992e"
>> -SRC_URI[sha256sum] = "e6373913142338d10515daf619d659433bfd2989988198930c13b0945a15e98a"
>> +SRC_URI[md5sum] = "b7b37117eecbdfaaf3075acfb063d5a3"
>> +SRC_URI[sha256sum] = "98a7dff3a1a6708c79789de8b9a05d8042e867067f70e8f30387c15026233219"
>>
>> S = "${WORKDIR}/Mesa-${PV}"
>>
>> diff --git a/meta/recipes-graphics/mesa/mesa_git.bb b/meta/recipes-graphics/mesa/mesa_git.bb
>> index b046ae2..e554ff4 100644
>> --- a/meta/recipes-graphics/mesa/mesa_git.bb
>> +++ b/meta/recipes-graphics/mesa/mesa_git.bb
>> @@ -4,8 +4,8 @@ DEFAULT_PREFERENCE = "-1"
>>
>> LIC_FILES_CHKSUM = "file://docs/license.html;md5=6a23445982a7a972ac198e93cc1cb3de"
>>
>> -SRCREV = "c7b9a2e38a3e471562b50dab8be65db8ac6819f8"
>> -PV = "10.3.4+git${SRCPV}"
>> +SRCREV = "f70e4d4afd16e66506ce3b055edb3b71b1464890"
>> +PV = "10.4.3+git${SRCPV}"
> that's the commit for 10.4.3 tag, this isn't consistent with the
> change you did in the non _git recipe.
_git version include the latest stable version of mesa.
So that's why we keep 2 versions.
Pengyu
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [V2][PATCH] mesa: Upgrade to 10.4.0
2015-01-29 10:05 ` Pengyu Ma
@ 2015-01-29 10:10 ` Nicolas Dechesne
2015-01-29 10:35 ` Burton, Ross
0 siblings, 1 reply; 11+ messages in thread
From: Nicolas Dechesne @ 2015-01-29 10:10 UTC (permalink / raw)
To: Pengyu Ma; +Cc: Patches and discussions about the oe-core layer
On Thu, Jan 29, 2015 at 11:05 AM, Pengyu Ma <pengyu.ma@windriver.com> wrote:
> On 01/29/2015 05:53 PM, Nicolas Dechesne wrote:
>>
>> On Wed, Jan 28, 2015 at 9:57 AM, Pengyu Ma <pengyu.ma@windriver.com>
>> wrote:
>>>
>>> diff --git a/meta/recipes-graphics/mesa/mesa-gl_10.3.4.bb
>>> b/meta/recipes-graphics/mesa/mesa-gl_10.4.0.bb
>>> similarity index 100%
>>> rename from meta/recipes-graphics/mesa/mesa-gl_10.3.4.bb
>>> rename to meta/recipes-graphics/mesa/mesa-gl_10.4.0.bb
>>> diff --git a/meta/recipes-graphics/mesa/mesa_10.3.4.bb
>>> b/meta/recipes-graphics/mesa/mesa_10.4.0.bb
>>> similarity index 78%
>>> rename from meta/recipes-graphics/mesa/mesa_10.3.4.bb
>>> rename to meta/recipes-graphics/mesa/mesa_10.4.0.bb
>>
>> why not 10.4.3 directly, instead?
>
> 10.4.0 is intel graphic stack 2014 Q4 Release version
> https://01.org/linuxgraphics/downloads/2014/2014q4-intel-graphics-stack-release
>
> It is stable and verified with other packages libdrm xorg-video-intel and
> xserver-xorg in oe-core master.
well, i am not sure this is right... at least probably not the right
argument. oe-core is not meant to be tied to specific intel stable
releases, whether it is about content or schedule..
i would believe our goal is to provide the most recent stable release
instead. so that each OE (well, Yocto) release ends up with the most
recent versions.
fwiw, for the boards/platforms i care about, 10.4.3 would be fine.
>>
>>
>>
>>> index 50092c9..7d3723e 100644
>>> --- a/meta/recipes-graphics/mesa/mesa_10.3.4.bb
>>> +++ b/meta/recipes-graphics/mesa/mesa_10.4.0.bb
>>> @@ -2,8 +2,8 @@ require ${BPN}.inc
>>>
>>> SRC_URI =
>>> "ftp://ftp.freedesktop.org/pub/mesa/${PV}/MesaLib-${PV}.tar.bz2"
>>>
>>> -SRC_URI[md5sum] = "fa0558a3d02c2bb8c208c030ccdc992e"
>>> -SRC_URI[sha256sum] =
>>> "e6373913142338d10515daf619d659433bfd2989988198930c13b0945a15e98a"
>>> +SRC_URI[md5sum] = "b7b37117eecbdfaaf3075acfb063d5a3"
>>> +SRC_URI[sha256sum] =
>>> "98a7dff3a1a6708c79789de8b9a05d8042e867067f70e8f30387c15026233219"
>>>
>>> S = "${WORKDIR}/Mesa-${PV}"
>>>
>>> diff --git a/meta/recipes-graphics/mesa/mesa_git.bb
>>> b/meta/recipes-graphics/mesa/mesa_git.bb
>>> index b046ae2..e554ff4 100644
>>> --- a/meta/recipes-graphics/mesa/mesa_git.bb
>>> +++ b/meta/recipes-graphics/mesa/mesa_git.bb
>>> @@ -4,8 +4,8 @@ DEFAULT_PREFERENCE = "-1"
>>>
>>> LIC_FILES_CHKSUM =
>>> "file://docs/license.html;md5=6a23445982a7a972ac198e93cc1cb3de"
>>>
>>> -SRCREV = "c7b9a2e38a3e471562b50dab8be65db8ac6819f8"
>>> -PV = "10.3.4+git${SRCPV}"
>>> +SRCREV = "f70e4d4afd16e66506ce3b055edb3b71b1464890"
>>> +PV = "10.4.3+git${SRCPV}"
>>
>> that's the commit for 10.4.3 tag, this isn't consistent with the
>> change you did in the non _git recipe.
>
> _git version include the latest stable version of mesa.
> So that's why we keep 2 versions.
ok, that makes sense. i wasn't sure about what the _git was supposed to be.
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: [V2][PATCH] mesa: Upgrade to 10.4.0
2015-01-29 10:10 ` Nicolas Dechesne
@ 2015-01-29 10:35 ` Burton, Ross
2015-01-30 1:51 ` Pengyu Ma
0 siblings, 1 reply; 11+ messages in thread
From: Burton, Ross @ 2015-01-29 10:35 UTC (permalink / raw)
To: Nicolas Dechesne; +Cc: Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
On 29 January 2015 at 10:10, Nicolas Dechesne <nicolas.dechesne@linaro.org>
wrote:
> well, i am not sure this is right... at least probably not the right
> argument. oe-core is not meant to be tied to specific intel stable
> releases, whether it is about content or schedule..
>
> i would believe our goal is to provide the most recent stable release
> instead. so that each OE (well, Yocto) release ends up with the most
> recent versions.
>
> fwiw, for the boards/platforms i care about, 10.4.3 would be fine.
>
Agreed. The Intel driver release is tested with 10.4.0 but 10.4.3 is a
newer point release so should work, and Intel's aim of ensuring that the
latest driver stack is supported doesn't trump having the latest upstream
releases in oe-core.
If it turns out that 10.4.3 is critically broken with the Intel driver then
*meta-intel* can ship 10.4.0.
Please re-submit this with 10.4.3 instead of 10.4.0.
Ross
[-- Attachment #2: Type: text/html, Size: 1408 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [V2][PATCH] mesa: Upgrade to 10.4.0
2015-01-29 10:35 ` Burton, Ross
@ 2015-01-30 1:51 ` Pengyu Ma
2015-01-30 7:51 ` Nicolas Dechesne
0 siblings, 1 reply; 11+ messages in thread
From: Pengyu Ma @ 2015-01-30 1:51 UTC (permalink / raw)
To: Burton, Ross, Nicolas Dechesne
Cc: Patches and discussions about the oe-core layer
[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]
On 01/29/2015 06:35 PM, Burton, Ross wrote:
>
> On 29 January 2015 at 10:10, Nicolas Dechesne
> <nicolas.dechesne@linaro.org <mailto:nicolas.dechesne@linaro.org>> wrote:
>
> well, i am not sure this is right... at least probably not the right
> argument. oe-core is not meant to be tied to specific intel stable
> releases, whether it is about content or schedule..
>
> i would believe our goal is to provide the most recent stable release
> instead. so that each OE (well, Yocto) release ends up with the most
> recent versions.
>
> fwiw, for the boards/platforms i care about, 10.4.3 would be fine.
>
>
> Agreed. The Intel driver release is tested with 10.4.0 but 10.4.3 is
> a newer point release so should work, and Intel's aim of ensuring that
> the latest driver stack is supported doesn't trump having the latest
> upstream releases in oe-core.
>
> If it turns out that 10.4.3 is critically broken with the Intel driver
> then *meta-intel* can ship 10.4.0.
>
> Please re-submit this with 10.4.3 instead of 10.4.0.
>
mesa_git bb will keep sync the latest version 10.4.3, that's why we keep
both _git and 10.4.0.
Now all all the version of xorg-video-intel, libdrm, and xserver-xorg
are the same with Intel Graphic stack 2014 Q4.
So mesa_10.4.0 will make a stable and verified solution here,
and _git version will make the latest version here.
Pengyu
> Ross
[-- Attachment #2: Type: text/html, Size: 3255 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [V2][PATCH] mesa: Upgrade to 10.4.0
2015-01-30 1:51 ` Pengyu Ma
@ 2015-01-30 7:51 ` Nicolas Dechesne
2015-01-30 7:56 ` Pengyu Ma
0 siblings, 1 reply; 11+ messages in thread
From: Nicolas Dechesne @ 2015-01-30 7:51 UTC (permalink / raw)
To: Pengyu Ma; +Cc: Patches and discussions about the oe-core layer
On Fri, Jan 30, 2015 at 2:51 AM, Pengyu Ma <pengyu.ma@windriver.com> wrote:
> mesa_git bb will keep sync the latest version 10.4.3, that's why we keep
> both _git and 10.4.0.
> Now all all the version of xorg-video-intel, libdrm, and xserver-xorg are
> the same with Intel Graphic stack 2014 Q4.
> So mesa_10.4.0 will make a stable and verified solution here,
> and _git version will make the latest version here.
>
i think you missed the point. you cannot justify the need for 10.4.0
because it is the 'prefered' Intel version. the policy is that we
provide in OE-core the most recent stable releases of upstream
components. when/if I need a specific version of mesa (or anything
else) for my project, i have a recipe in my own project layer, but
OE-core is agnostic to that.
now, if a specific version of mesa is known to be broken, upstream, or
in very special circumstances, we might want to not use it... but that
isn't the case here, especially since both Ross and I are asking you
to upgrade to 10.4.3..
if you don't submit 10.4.3, someone else will anyways. and actually i
have submitted a libdrm upgrade yesterday which is likely to be merged
soon..
cheers
nicolas
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [V2][PATCH] mesa: Upgrade to 10.4.0
2015-01-30 7:51 ` Nicolas Dechesne
@ 2015-01-30 7:56 ` Pengyu Ma
2015-01-30 8:02 ` Nicolas Dechesne
0 siblings, 1 reply; 11+ messages in thread
From: Pengyu Ma @ 2015-01-30 7:56 UTC (permalink / raw)
To: Nicolas Dechesne; +Cc: Patches and discussions about the oe-core layer
On 01/30/2015 03:51 PM, Nicolas Dechesne wrote:
> On Fri, Jan 30, 2015 at 2:51 AM, Pengyu Ma <pengyu.ma@windriver.com> wrote:
>> mesa_git bb will keep sync the latest version 10.4.3, that's why we keep
>> both _git and 10.4.0.
>> Now all all the version of xorg-video-intel, libdrm, and xserver-xorg are
>> the same with Intel Graphic stack 2014 Q4.
>> So mesa_10.4.0 will make a stable and verified solution here,
>> and _git version will make the latest version here.
>>
> i think you missed the point. you cannot justify the need for 10.4.0
> because it is the 'prefered' Intel version. the policy is that we
> provide in OE-core the most recent stable releases of upstream
> components. when/if I need a specific version of mesa (or anything
> else) for my project, i have a recipe in my own project layer, but
> OE-core is agnostic to that.
>
> now, if a specific version of mesa is known to be broken, upstream, or
> in very special circumstances, we might want to not use it... but that
> isn't the case here, especially since both Ross and I are asking you
> to upgrade to 10.4.3..
>
> if you don't submit 10.4.3, someone else will anyways. and actually i
> have submitted a libdrm upgrade yesterday which is likely to be merged
> soon..
Understood, but there are 2 version mesa_xxx.bb and mesa_git.bb.
Is there any reason why keep two versions?
If I updated mesa_xxx.bb to 10.4.3, it will be the same as mesa_git.bb.
Regards,
Pengyu
>
> cheers
> nicolas
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [V2][PATCH] mesa: Upgrade to 10.4.0
2015-01-30 7:56 ` Pengyu Ma
@ 2015-01-30 8:02 ` Nicolas Dechesne
2015-01-30 9:05 ` Richard Purdie
0 siblings, 1 reply; 11+ messages in thread
From: Nicolas Dechesne @ 2015-01-30 8:02 UTC (permalink / raw)
To: Pengyu Ma; +Cc: Patches and discussions about the oe-core layer
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.
> If I updated mesa_xxx.bb to 10.4.3, it will be the same as mesa_git.bb.
yep, like it is today...
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [V2][PATCH] mesa: Upgrade to 10.4.0
2015-01-30 8:02 ` Nicolas Dechesne
@ 2015-01-30 9:05 ` Richard Purdie
2015-01-30 9:12 ` Pengyu Ma
0 siblings, 1 reply; 11+ messages in thread
From: Richard Purdie @ 2015-01-30 9:05 UTC (permalink / raw)
To: Nicolas Dechesne; +Cc: Patches and discussions about the oe-core layer
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
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [V2][PATCH] mesa: Upgrade to 10.4.0
2015-01-30 9:05 ` Richard Purdie
@ 2015-01-30 9:12 ` Pengyu Ma
0 siblings, 0 replies; 11+ messages in thread
From: Pengyu Ma @ 2015-01-30 9:12 UTC (permalink / raw)
To: Richard Purdie, Nicolas Dechesne
Cc: Patches and discussions about the oe-core layer
On 01/30/2015 05:05 PM, Richard Purdie wrote:
> 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.
Thanks for kindly explanation, it makes more clear about _git.
I will re-submit another mesa_10.4.3 and same _git version.
Thanks,
Pengyu
> Cheers,
>
> Richard
>
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2015-01-30 9:12 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2015-01-30 9:12 ` Pengyu Ma
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox