u-boot-fslc: Add tag to git SRC_URI
PATCH 1/1 u-boot-fslc: Add tag to git SRC_URI
From: Dan McGregor <[email protected]>
Bitbake now checks for the commit in the master branch by default. Explictly set the tag where SRCREV is expected.
--- recipes-bsp/u-boot/u-boot-fslc_2013.10.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
recipes-bsp/u-boot/u-boot-fslc_2013.10.bb +1 -1
@@ -11,7 +11,7 @@ PROVIDES += "u-boot" PV = "v2013.10" SRCREV = "079e214888279518ce061c71238a74a0c3db2c28" -SRC_URI = "git://github.com/Freescale/u-boot-imx.git" +SRC_URI = "git://github.com/Freescale/u-boot-imx.git;tag=patches-2013.10" S = "${WORKDIR}/git"
Signature · 1 line
1.7.9.5
Quoted 16 lines · John Weber
From: Dan McGregor <[email protected]>
Bitbake now checks for the commit in the master branch by default. Explictly set the tag where SRCREV is expected.
Signed-off-by John Weber <[email protected]>--- recipes-bsp/u-boot/u-boot-fslc_2013.10.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)recipes-bsp/u-boot/u-boot-fslc_2013.10.bb +0
-0
recipes-bsp/u-boot/u-boot-fslc_2013.10.bb PROVIDES += "u-boot" · line 17
Quoted 8 lines
recipes-bsp/u-boot/u-boot-fslc_2013.10.bb +1
-1@@ -11,7 +11,7 @@ PROVIDES += "u-boot" PV = "v2013.10" SRCREV = "079e214888279518ce061c71238a74a0c3db2c28" -SRC_URI = "git://github.com/Freescale/u-boot-imx.git" +SRC_URI = "git://github.com/Freescale/u-boot-imx.git;tag=patches-2013.10" S = "${WORKDIR}/git"
Can you please change this so the branch name can be overridden, as in the patches I sent for the other recipes?
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 22 lines · Gary Thomas
Quoted 21 lines · John Weber
From: Dan McGregor <[email protected]>
Bitbake now checks for the commit in the master branch by default. Explictly set the tag where SRCREV is expected.
Signed-off-by John Weber <[email protected]>--- recipes-bsp/u-boot/u-boot-fslc_2013.10.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)recipes-bsp/u-boot/u-boot-fslc_2013.10.bb +1
-1@@ -11,7 +11,7 @@ PROVIDES += "u-boot" PV = "v2013.10" SRCREV = "079e214888279518ce061c71238a74a0c3db2c28" -SRC_URI = "git://github.com/Freescale/u-boot-imx.git" +SRC_URI = "git://github.com/Freescale/u-boot-imx.git;tag=patches-2013.10"
Quoted 8 lines
recipes-bsp/u-boot/u-boot-fslc_2013.10.bb PROVIDES += "u-boot" · line 17
Quoted 3 lines
recipes-bsp/u-boot/u-boot-fslc_2013.10.bb +0
-0S = "${WORKDIR}/git"Can you please change this so the branch name can be overridden, as in the patches I sent for the other recipes?
Hi Gary - I'm not sure if that would be useful since the u-boot recipe does not depend on a .inc file. Where would the override come from?
Quoted 31 lines · John Weber
Quoted 22 lines · Gary Thomas
Quoted 21 lines · John Weber
From: Dan McGregor <[email protected]>
Bitbake now checks for the commit in the master branch by default. Explictly set the tag where SRCREV is expected.
Signed-off-by John Weber <[email protected]>--- recipes-bsp/u-boot/u-boot-fslc_2013.10.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)recipes-bsp/u-boot/u-boot-fslc_2013.10.bb +1
-1@@ -11,7 +11,7 @@ PROVIDES += "u-boot" PV = "v2013.10" SRCREV = "079e214888279518ce061c71238a74a0c3db2c28" -SRC_URI = "git://github.com/Freescale/u-boot-imx.git" +SRC_URI = "git://github.com/Freescale/u-boot-imx.git;tag=patches-2013.10"Quoted 8 lines
recipes-bsp/u-boot/u-boot-fslc_2013.10.bb PROVIDES += "u-boot" · line 17
Quoted 3 lines
recipes-bsp/u-boot/u-boot-fslc_2013.10.bb +0
-0S = "${WORKDIR}/git"Can you please change this so the branch name can be overridden, as in the patches I sent for the other recipes?
Quoted 1 line
Hi Gary - I'm not sure if that would be useful since the u-boot recipe does not depend on a .inc file. Where would the override come from?
From .bbappend files in my layers (I have a private BSP layer which extend the meta-fsl-arm* layers).
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Hello Gary,
Quoted 37 lines · Gary Thomas
Quoted 36 lines · John Weber
Quoted 34 lines · Gary Thomas
Quoted 24 lines · John Weber
From: Dan McGregor <[email protected]>
Bitbake now checks for the commit in the master branch by default. Explictly set the tag where SRCREV is expected.
Signed-off-by John Weber <[email protected]>--- recipes-bsp/u-boot/u-boot-fslc_2013.10.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)recipes-bsp/u-boot/u-boot-fslc_2013.10.bb +1
-1@@ -11,7 +11,7 @@ PROVIDES += "u-boot" PV = "v2013.10" SRCREV = "079e214888279518ce061c71238a74a0c3db2c28" -SRC_URI = "git://github.com/Freescale/u-boot-imx.git" +SRC_URI ="
git://github.com/Freescale/u-boot-imx.git;tag=patches-2013.10"Quoted 3 lines
S = "${WORKDIR}/git"Can you please change this so the branch name can be overridden, as in the patches I sent for the other recipes?
Quoted 6 lines
Quoted 2 lines
Hi Gary - I'm not sure if that would be useful since the u-boot recipe does not depend on a .inc file. Where would the override come from?
From .bbappend files in my layers (I have a private BSP layer which extend the meta-fsl-arm* layers).
I think what John means is that you'll end rewriting the SRC_URI, no?
Do you have an use example where you'd need it?
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 36 lines · Otavio Salvador
Hello Gary,
Quoted 33 lines · Gary Thomas
Quoted 32 lines · John Weber
Quoted 31 lines · Gary Thomas
Quoted 23 lines · John Weber
From: Dan McGregor <[email protected]>
Bitbake now checks for the commit in the master branch by default. Explictly set the tag where SRCREV is expected.
Signed-off-by John Weber <[email protected]>--- recipes-bsp/u-boot/u-boot-fslc_2013.10.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)recipes-bsp/u-boot/u-boot-fslc_2013.10.bb +1
-1@@ -11,7 +11,7 @@ PROVIDES += "u-boot" PV = "v2013.10" SRCREV = "079e214888279518ce061c71238a74a0c3db2c28" -SRC_URI = "git://github.com/Freescale/u-boot-imx.git" +SRC_URI ="
git://github.com/Freescale/u-boot-imx.git;tag=patches-2013.10"Quoted 3 lines
S = "${WORKDIR}/git"Can you please change this so the branch name can be overridden, as in the patches I sent for the other recipes?
Quoted 9 lines
Quoted 5 lines
Quoted 2 lines
Hi Gary - I'm not sure if that would be useful since the u-boot recipe does not depend on a .inc file. Where would the override come from?
From .bbappend files in my layers (I have a private BSP layer which
extend the meta-fsl-arm* layers).I think what John means is that you'll end rewriting the
SRC_URI, no?Do you have an use example where you'd need it?
I think he means to do something like this:
GITTAG ??= "patches-2013.10"SRC_URI = "git://github.com/Freescale/u-boot-imx.git;tag=${GITTAG}"
This way he can override GITTAG in his .bbappend, correct?
Quoted 45 lines · John Weber
Quoted 43 lines · Otavio Salvador
Hello Gary,
Quoted 33 lines · Gary Thomas
Quoted 32 lines · John Weber
Quoted 31 lines · Gary Thomas
Quoted 23 lines · John Weber
From: Dan McGregor <[email protected]>
Bitbake now checks for the commit in the master branch by default. Explictly set the tag where SRCREV is expected.
Signed-off-by John Weber <[email protected]>--- recipes-bsp/u-boot/u-boot-fslc_2013.10.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)recipes-bsp/u-boot/u-boot-fslc_2013.10.bb +1
-1@@ -11,7 +11,7 @@ PROVIDES += "u-boot" PV = "v2013.10" SRCREV = "079e214888279518ce061c71238a74a0c3db2c28" -SRC_URI = "git://github.com/Freescale/u-boot-imx.git" +SRC_URI ="
git://github.com/Freescale/u-boot-imx.git;tag=patches-2013.10"Quoted 3 lines
S = "${WORKDIR}/git"Can you please change this so the branch name can be overridden, as in the patches I sent for the other recipes?
Quoted 5 lines
Quoted 2 lines
Hi Gary - I'm not sure if that would be useful since the u-boot recipe does not depend on a .inc file. Where would the override come from?
From .bbappend files in my layers (I have a private BSP layer which
extend the meta-fsl-arm* layers).I think what John means is that you'll end rewriting the
SRC_URI, no?
Quoted 8 lines
Quoted 2 lines
Do you have an use example where you'd need it?
I think he means to do something like this:
GITTAG ??= "patches-2013.10"
SRC_URI= "git://github.com/Freescale/u-boot-imx.git;tag=${GITTAG}"This way he can override GITTAG in his .bbappend, correct?
Correct. The ??= isn't even necessary since the .bbappend can always override it.
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 11 lines · Gary Thomas
Quoted 8 lines
Quoted 2 lines
Do you have an use example where you'd need it?
I think he means to do something like this:
GITTAG ??= "patches-2013.10"
SRC_URI= "git://github.com/Freescale/u-boot-imx.git;tag=${GITTAG}"This way he can override GITTAG in his .bbappend, correct?
Correct. The ??= isn't even necessary since the .bbappend can always override it.
In this case you're using an old version of the bootloader in your internal BSP, right? I'd expect you to add an .bb file for this version instead and use PREFERRED_VERSION to use it.
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 8 lines · Otavio Salvador
Quoted 7 lines · Gary Thomas
Quoted 7 lines
Quoted 2 lines
Do you have an use example where you'd need it?
I think he means to do something like this:
GITTAG ??= "patches-2013.10"
SRC_URI= "git://github.com/Freescale/u-boot-imx.git;tag=${GITTAG}"
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
This way he can override GITTAG in his .bbappend, correct?
Correct. The ??= isn't even necessary since the .bbappend can always override it.
In this case you're using an old version of the bootloader in your internal BSP, right? I'd expect you to add an .bb file for this version instead and use
PREFERRED_VERSIONto use it.
Why should I do that when .bbappend works perfectly well? I can also see this as a case when new boards are added or old ones are still around and they get updated on different schedules.
Also, what does it hurt to be flexible?
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 23 lines · Gary Thomas
Quoted 13 lines · Otavio Salvador
Quoted 11 lines · Gary Thomas
Quoted 9 lines
Quoted 3 lines
Do you have an use example where you'd need it?
I think he means to do something like this:
GITTAG ??= "patches-2013.10"
SRC_URI= "git://github.com/Freescale/u-boot-imx.git;tag=${GITTAG}"This way he can override GITTAG in his .bbappend, correct?
Quoted 7 lines
Quoted 2 lines
Correct. The ??= isn't even necessary since the .bbappend can always override it.
In this case you're using an old version of the bootloader in your internal BSP, right? I'd expect you to add an .bb file for this version instead and use
PREFERRED_VERSIONto use it.
Quoted 5 lines
Why should I do that when .bbappend works perfectly well? I can also see this as a case when new boards are added or old ones are still around and they get updated on different schedules.
Also, what does it hurt to be flexible?
In this case you'd have a 2013.10 recipe building/installing a 2013.04 version for example, this is misleading and confusing for someone using the BSP.
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 19 lines · Otavio Salvador
Quoted 18 lines · Gary Thomas
Quoted 16 lines · Otavio Salvador
Quoted 11 lines · Gary Thomas
Quoted 8 lines
Quoted 2 lines
Do you have an use example where you'd need it?
I think he means to do something like this:
GITTAG ??= "patches-2013.10"
SRC_URI= "git://github.com/Freescale/u-boot-imx.git;tag=${GITTAG}"This way he can override GITTAG in his .bbappend, correct?
Correct. The ??= isn't even necessary since the .bbappend can always override it.
In this case you're using an old version of the bootloader in your internal BSP, right? I'd expect you to add an .bb file for this version instead and use
PREFERRED_VERSIONto use it.
Quoted 9 lines
Quoted 5 lines
Why should I do that when .bbappend works perfectly well? I can also see this as a case when new boards are added or old ones are still around and they get updated on different schedules.
Also, what does it hurt to be flexible?
In this case you'd have a 2013.10 recipe building/installing a 2013.04 version for example, this is misleading and confusing for someone using the BSP.
I sent a v2 so that the tag is able to be overridden. Otavio can make the call if he would like to take the original or the v2. It seems to me that it might be good to separate the SRC_URI into a .inc file for U-boot the way it is done for the kernel.
Quoted 34 lines · John Weber
Quoted 32 lines · Otavio Salvador
Quoted 29 lines · Gary Thomas
Quoted 13 lines · Otavio Salvador
Quoted 11 lines · Gary Thomas
Quoted 9 lines
Quoted 3 lines
Do you have an use example where you'd need it?
I think he means to do something like this:
GITTAG ??= "patches-2013.10"
SRC_URI= "git://github.com/Freescale/u-boot-imx.git;tag=${GITTAG}"This way he can override GITTAG in his .bbappend, correct?
Quoted 7 lines
Quoted 2 lines
Correct. The ??= isn't even necessary since the .bbappend can always override it.
In this case you're using an old version of the bootloader in your internal BSP, right? I'd expect you to add an .bb file for this version instead and use
PREFERRED_VERSIONto use it.Why should I do that when .bbappend works perfectly well? I can also see this as a case when new boards are added or old ones are still around and they get updated on different schedules.
Also, what does it hurt to be flexible?
Quoted 8 lines
Quoted 4 lines
In this case you'd have a 2013.10 recipe building/installing a 2013.04 version for example, this is misleading and confusing for someone using the BSP.
I sent a v2 so that the tag is able to be overridden. Otavio can make the call if he would like to take the original or the v2. It seems to me that it might be good to separate the
SRC_URIinto a .inc file for U-boot the way it is done for the kernel.
This proposed solution seem to be the cleanest one. Would you mind to rework it this way?
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 28 lines · Otavio Salvador
Quoted 27 lines · Gary Thomas
Quoted 13 lines · Otavio Salvador
Quoted 11 lines · Gary Thomas
Quoted 9 lines
Quoted 3 lines
Do you have an use example where you'd need it?
I think he means to do something like this:
GITTAG ??= "patches-2013.10"
SRC_URI= "git://github.com/Freescale/u-boot-imx.git;tag=${GITTAG}"This way he can override GITTAG in his .bbappend, correct?
Quoted 7 lines
Quoted 2 lines
Correct. The ??= isn't even necessary since the .bbappend can always override it.
In this case you're using an old version of the bootloader in your internal BSP, right? I'd expect you to add an .bb file for this version instead and use
PREFERRED_VERSIONto use it.Why should I do that when .bbappend works perfectly well? I can also see this as a case when new boards are added or old ones are still around and they get updated on different schedules.
Quoted 6 lines
Quoted 1 line
Also, what does it hurt to be flexible?
In this case you'd have a 2013.10 recipe building/installing a 2013.04 version for example, this is misleading and confusing for someone using the BSP.
You do what you want - I just hope that I don't end up having to clone all of meta-fsl-arm* just because you fear a little flexibility :-(
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 39 lines · Gary Thomas
Quoted 38 lines · Otavio Salvador
Quoted 34 lines · Gary Thomas
Quoted 16 lines · Otavio Salvador
Quoted 13 lines · Gary Thomas
Quoted 10 lines
Quoted 4 lines
Do you have an use example where you'd need it?
I think he means to do something like this:
GITTAG ??= "patches-2013.10"
SRC_URI= "git://github.com/Freescale/u-boot-imx.git;tag=${GITTAG}"This way he can override GITTAG in his .bbappend, correct?
Quoted 8 lines
Quoted 2 lines
Correct. The ??= isn't even necessary since the .bbappend can always override it.
In this case you're using an old version of the bootloader in your internal BSP, right? I'd expect you to add an .bb file for this version instead and use
PREFERRED_VERSIONto use it.Why should I do that when .bbappend works perfectly well? I can also see this as a case when new boards are added or old ones are still around and they get updated on different schedules.
Also, what does it hurt to be flexible?
Quoted 8 lines
Quoted 4 lines
In this case you'd have a 2013.10 recipe building/installing a 2013.04 version for example, this is misleading and confusing for someone using the BSP.
You do what you want - I just hope that I don't end up having to clone all of meta-fsl-arm* just because you fear a little flexibility :-(
I think you got me wrong.
The discussion here is to try to identify needs and try to come with clean solution which works most people while keep it clean and simple to understand as possible.
I think it is quite confusing when someone seems a bbappend which changes a recipe for an old version and this does not match the recipe name. I am fully aware this is /possible/ to do but this does not mean this is advisable or desired.
I think that John's proposed solution is going to address both concerns well.
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 55 lines · Otavio Salvador
Quoted 39 lines · Gary Thomas
Quoted 38 lines · Otavio Salvador
Quoted 34 lines · Gary Thomas
Quoted 16 lines · Otavio Salvador
Quoted 13 lines · Gary Thomas
Quoted 10 lines
Quoted 4 lines
Do you have an use example where you'd need it?
I think he means to do something like this:
GITTAG ??= "patches-2013.10"
SRC_URI= "git://github.com/Freescale/u-boot-imx.git;tag=${GITTAG}"This way he can override GITTAG in his .bbappend, correct?
Quoted 8 lines
Quoted 2 lines
Correct. The ??= isn't even necessary since the .bbappend can always override it.
In this case you're using an old version of the bootloader in your internal BSP, right? I'd expect you to add an .bb file for this version instead and use
PREFERRED_VERSIONto use it.Why should I do that when .bbappend works perfectly well? I can also see this as a case when new boards are added or old ones are still around and they get updated on different schedules.
Also, what does it hurt to be flexible?
Quoted 8 lines
Quoted 4 lines
In this case you'd have a 2013.10 recipe building/installing a 2013.04 version for example, this is misleading and confusing for someone using the BSP.
You do what you want - I just hope that I don't end up having to clone all of meta-fsl-arm* just because you fear a little flexibility :-(
I think you got me wrong.
The discussion here is to try to identify needs and try to come with clean solution which works most people while keep it clean and simple to understand as possible.
Quoted 7 lines
I think it is quite confusing when someone seems a bbappend which changes a recipe for an old version and this does not match the recipe name. I am fully aware this is /possible/ to do but this does not mean this is advisable or desired.
I think that John's proposed solution is going to address both concerns well.
Here's what I want to be able to support: I'm building my
own targets (actual hardware) and I start from some version of u-boot-fslc, linux-boundary, etc. My local working copies of that are based on a particular version and I want to still use the same recipes from meta-fsl-arm* even if they are updated for more recent versions. This is even more important for the kernel. I have boards that are based on boundary-imx_3.0.35_4.0.0 but the meta-fsl-arm* recipes are now based on boundary-imx_3.0.35_4.1.0. Note that the recipe linux-boundary_3.0.35.bb didn't change names or even version numbers when the branch was changed. Without the ability to override the branch in my .bbappend, I can't use the meta-fsl-arm* recipe at all and would end up having to clone it which is really bad/unacceptable.
I would not be using this in a way that the version being built was different than the recipe version implied. If, for example, meta-fsl-arm* replaces u-boot-fslc_2013.10.bb with u-boot-fslc_2013.12.bb (and dropped the older u-boot-fslc_2013.10.bb), just like you I would not find it acceptable to use .bbappend to go back to the 2013.10 branch/version. In that case, I would clone the 2013.10 recipe into my own layer(s). I just try to use the main layers as much as possible.
Signature · 4 lines
---------------------------------------------------------- Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 90 lines · Gary Thomas
Quoted 66 lines · Otavio Salvador
Quoted 48 lines · Gary Thomas
Quoted 46 lines · Otavio Salvador
Quoted 40 lines · Gary Thomas
Quoted 25 lines · Otavio Salvador
Quoted 10 lines · Gary Thomas
Quoted 10 lines
Quoted 5 lines
Do you have an use example where you'd need it?
I think he means to do something like this:
GITTAG ??= "patches-2013.10"
SRC_URI= "git://github.com/Freescale/u-boot-imx.git;tag=${GITTAG}"Quoted 7 lines
Quoted 1 line
This way he can override GITTAG in his .bbappend, correct?
Correct. The ??= isn't even necessary since the .bbappend can always override it.
Quoted 3 lines
In this case you're using an old version of the bootloader in your internal BSP, right? I'd expect you to add an .bb file for this version instead and use
PREFERRED_VERSIONto use it.Why should I do that when .bbappend works perfectly well? I can also see this as a case when new boards are added or old ones are still around and they get updated on different schedules.
Also, what does it hurt to be flexible?
Quoted 8 lines
Quoted 4 lines
In this case you'd have a 2013.10 recipe building/installing a 2013.04 version for example, this is misleading and confusing for someone using the BSP.
You do what you want - I just hope that I don't end up having to clone all of meta-fsl-arm* just because you fear a little flexibility :-(
I think you got me wrong.
The discussion here is to try to identify needs and try to come with clean solution which works most people while keep it clean and simple to understand as possible.
Quoted 8 lines
I think it is quite confusing when someone seems a bbappend which changes a recipe for an old version and this does not match the recipe name. I am fully aware this is /possible/ to do but this does not mean this is advisable or desired.
I think that John's proposed solution is going to address both concerns well.
Here's what I want to be able to support: I'm building my
own targets (actual hardware) and I start from some version of u-boot-fslc, linux-boundary, etc. My local working copies of that are based on a particular version and I want to still use the same recipes from meta-fsl-arm* even if they are updated for more recent versions. This is even more important for the kernel. I have boards that are based on boundary-imx_3.0.35_4.0.0 but the meta-fsl-arm* recipes are now based on boundary-imx_3.0.35_4.1.0. Note that the recipe linux-boundary_3.0.35.bb didn't change names or even version numbers when the branch was changed. Without the ability to override the branch in my .bbappend, I can't use the meta-fsl-arm* recipe at all and would end up having to clone it which is really bad/unacceptable.
Quoted 7 lines
I would not be using this in a way that the version being built was different than the recipe version implied. If, for example, meta-fsl-arm* replaces u-boot-fslc_2013.10.bb with u-boot-fslc_2013.12.bb (and dropped the older u-boot-fslc_2013.10.bb), just like you I would not find it acceptable to use .bbappend to go back to the 2013.10 branch/version. In that case, I would clone the 2013.10 recipe into my own layer(s). I just try to use the main layers as much as possible.
Right but I fail to understand how changing branch will make it work for you if you're using a repository which you cannot push...
All the rest I fully agree.
Signature · 3 lines
Otavio Salvador O.S. Systems http://www.ossystems.com.br http://code.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
Quoted 32 lines · Gary Thomas
Quoted 31 lines · John Weber
Quoted 30 lines · Gary Thomas
Quoted 16 lines · John Weber
From: Dan McGregor <[email protected]>
Bitbake now checks for the commit in the master branch by default. Explictly set the tag where SRCREV is expected.
Signed-off-by John Weber <[email protected]>--- recipes-bsp/u-boot/u-boot-fslc_2013.10.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)recipes-bsp/u-boot/u-boot-fslc_2013.10.bb +0
-0recipes-bsp/u-boot/u-boot-fslc_2013.10.bb PROVIDES += "u-boot" · line 17
Quoted 8 lines
recipes-bsp/u-boot/u-boot-fslc_2013.10.bb +1
-1@@ -11,7 +11,7 @@ PROVIDES += "u-boot" PV = "v2013.10" SRCREV = "079e214888279518ce061c71238a74a0c3db2c28" -SRC_URI = "git://github.com/Freescale/u-boot-imx.git" +SRC_URI = "git://github.com/Freescale/u-boot-imx.git;tag=patches-2013.10" S = "${WORKDIR}/git"Can you please change this so the branch name can be overridden, as in the patches I sent for the other recipes?
Quoted 5 lines
Quoted 1 line
Hi Gary - I'm not sure if that would be useful since the u-boot recipe does not depend on a .inc file. Where would the override come from?
From .bbappend files in my layers (I have a private BSP layer which extend the meta-fsl-arm* layers).
Ah. OK. Makes sense.