bitbake.conf: Stop providing ${P} and ${PF} by default
RFC PATCH 1/1 bitbake.conf: Stop providing ${P} and ${PF} by default
For a long time we've provided PN-PV and PN-PV-PR by tweaking PROVIDES. This looks nice at first glance however it turns out to be a bit problematic. Taking make as an example where there are two versions, 3.81 and 3.82, what should "bitbake make-3.81" do?
Currently it builds make-3.81 and make-3.82 and breaks in interesting ways. Is that a bitbake bug? Well, it certainly shouldn't try and run the build. Why is it building 3.82 though? Its due to finding a dependency on "make-dev" and then trying to figure out what provides it? The answer is "make" and the default version of "make" is 3.82.
So arguably, finding "make-3.81" should infer PREFERRED_VERSION_make = "3.81". Doing so resolved the above problem since now "make" resolves to "make-3.81".
So what about if we have Recipe A:
DEPENDS = "make-3.81"
and Recipe B:
DEPENDS = "make-3.82"
That is clearly an error, easy. So finally what about if we have Recipe A:
DEPENDS = "make-3.81"
and Recipe B:
DEPENDS = "make"
The first recipe infers the PREFERRED_VERSION_make = "3.81" and then forces that version on everything else. Is that desired? Probably not in most cases, at least not silently.
As mitigation, we could print a WARNING about this happening. The final part of the problem is that we can ony figure this out within bitbake itself. That means we'd have to teach bitbake about the PN-PV format of PROVIDES which is breaking the separation between bitbake and the metadata. We can't win :(.
Nobody that I know of is using or relying on this functionality so perhaps we should just remove it instead which is what this patch does. Opinions?
---
meta/conf/bitbake.conf +1 -1
@@ -253,7 +253,7 @@ DEPCHAIN_POST = "-dev -dbg" DEPENDS = "" RDEPENDS = "" PROVIDES = "" -PROVIDES_prepend = "${P} ${PF} ${PN} " +PROVIDES_prepend = "${PN} " RPROVIDES = "" MULTI_PROVIDER_WHITELIST = "virtual/libintl virtual/libintl-native virtual/nativesdk-libintl virtual/xserver virtual/update-alternatives-native virtual/update-alternatives"
Quoted 44 lines · Richard Purdie
For a long time we've provided PN-PV and PN-PV-PR by tweaking PROVIDES. This looks
nice at first glance however it turns out to be a bit problematic. Taking make as an
example where there are two versions, 3.81 and 3.82, what should "bitbake make-3.81" do?Currently it builds make-3.81 and make-3.82 and breaks in interesting ways. Is that
a bitbake bug? Well, it certainly shouldn't try and run the build. Why is it building
3.82 though? Its due to finding a dependency on "make-dev" and then trying to figure
out what provides it? The answer is "make" and the default version of "make" is 3.82.So arguably, finding "make-3.81" should infer
PREFERRED_VERSION_make= "3.81". Doing
so resolved the above problem since now "make" resolves to "make-3.81".So what about if we have Recipe A:
DEPENDS = "make-3.81"
and Recipe B:
DEPENDS = "make-3.82"That is clearly an error, easy. So finally what about if we have Recipe A:
DEPENDS = "make-3.81"
and Recipe B:
DEPENDS = "make"The first recipe infers the
PREFERRED_VERSION_make= "3.81" and then forces that
version on everything else. Is that desired? Probably not in most cases, at least not
silently.As mitigation, we could print a WARNING about this happening. The final part of the problem
is that we can ony figure this out within bitbake itself. That means we'd have to teach bitbake
about the PN-PV format of PROVIDES which is breaking the separation between bitbake and the
metadata. We can't win :(.
Quoted 6 lines
Nobody that I know of is using or relying on this functionality so perhaps we should
just remove it instead which is what this patch does. Opinions?Signed-off-by Richard Purdie <[email protected]>
This sounds like a good plan to me. We never *really* supported version specific build dependencies anyway, and using those provides just caused problems. Better for it to go away entirely.
Signature · 1 line
Christopher Larson
Hi RP,
Thanks, Can we provide a replacement for the "bitbake PN-PV" since it is useful, for example, can we support the PREFERRED_VERSION_${PN} in the env in the future ? There is a similar bug:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4965
// Robert
Quoted 57 lines · Richard Purdie
For a long time we've provided PN-PV and PN-PV-PR by tweaking PROVIDES. This looks nice at first glance however it turns out to be a bit problematic. Taking make as an example where there are two versions, 3.81 and 3.82, what should "bitbake make-3.81" do?
Currently it builds make-3.81 and make-3.82 and breaks in interesting ways. Is that a bitbake bug? Well, it certainly shouldn't try and run the build. Why is it building 3.82 though? Its due to finding a dependency on "make-dev" and then trying to figure out what provides it? The answer is "make" and the default version of "make" is 3.82.
So arguably, finding "make-3.81" should infer
PREFERRED_VERSION_make= "3.81". Doing so resolved the above problem since now "make" resolves to "make-3.81".So what about if we have Recipe A:
DEPENDS = "make-3.81"
and Recipe B:
DEPENDS = "make-3.82"That is clearly an error, easy. So finally what about if we have Recipe A:
DEPENDS = "make-3.81"
and Recipe B:
DEPENDS = "make"The first recipe infers the
PREFERRED_VERSION_make= "3.81" and then forces that version on everything else. Is that desired? Probably not in most cases, at least not silently.As mitigation, we could print a WARNING about this happening. The final part of the problem is that we can ony figure this out within bitbake itself. That means we'd have to teach bitbake about the PN-PV format of PROVIDES which is breaking the separation between bitbake and the metadata. We can't win :(.
Nobody that I know of is using or relying on this functionality so perhaps we should just remove it instead which is what this patch does. Opinions?
Signed-off-by Richard Purdie <[email protected]>---
meta/conf/bitbake.conf +1
-1@@ -253,7 +253,7 @@ DEPCHAIN_POST = "-dev -dbg" DEPENDS = "" RDEPENDS = "" PROVIDES = "" -PROVIDES_prepend = "${P} ${PF} ${PN} " +PROVIDES_prepend = "${PN} " RPROVIDES = "" MULTI_PROVIDER_WHITELIST = "virtual/libintl virtual/libintl-native virtual/nativesdk-libintl virtual/xserver virtual/update-alternatives-native virtual/update-alternatives"_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 5 lines · Robert Yang
Thanks, Can we provide a replacement for the "bitbake PN-PV" since it is useful, for example, can we support the PREFERRED_VERSION_${PN} in the env in the future ? There is a similar bug:
If you set BB_PRESERVE_ENV=1 you can set PREFERRED_VERSION_xxx from the environment so this should already be possible?
Cheers,
Richard
Quoted 10 lines · Richard Purdie
Quoted 5 lines · Robert Yang
Thanks, Can we provide a replacement for the "bitbake PN-PV" since it is useful, for example, can we support the PREFERRED_VERSION_${PN} in the env in the future ? There is a similar bug:
If you set BB_PRESERVE_ENV=1 you can set
PREFERRED_VERSION_xxxfrom the environment so this should already be possible?
It seems that the BB_PRESERVE_ENV=1 doesn't work, but we use the BB_ENV_EXTRAWHITE, for example:
$ export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE PREFERRED_VERSION_make" $ export PREFERRED_VERSION_make="3.81",
Then it works, maybe something is wrong with the BB_PRESERVE_ENV.
// Robert
Quoted 6 lines
Cheers,
Richard
Quoted 13 lines · Robert Yang
Quoted 10 lines · Richard Purdie
Quoted 5 lines · Robert Yang
Thanks, Can we provide a replacement for the "bitbake PN-PV" since it is useful, for example, can we support the PREFERRED_VERSION_${PN} in the env in the future ? There is a similar bug:
If you set BB_PRESERVE_ENV=1 you can set
PREFERRED_VERSION_xxxfrom the environment so this should already be possible?
Quoted 7 lines
It seems that the BB_PRESERVE_ENV=1 doesn't work, but we use the
BB_ENV_EXTRAWHITE, for example:$ export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE PREFERRED_VERSION_make" $ export PREFERRED_VERSION_make="3.81",Then it works, maybe something is wrong with the
BB_PRESERVE_ENV.
It is broken, yes, I've sent out a patch to fix it. There is one other problem, you can't use "-" in a shell environment variable so you can't do:
PREFERRED_VERSION_make-native = xxx
which is annoying. We might want to add some kind of mangling mechanism like a double underscore translating to a dash or something...
Cheers,
Richard
Quoted 17 lines · Richard Purdie
Quoted 16 lines · Robert Yang
Quoted 10 lines · Richard Purdie
Quoted 5 lines · Robert Yang
Thanks, Can we provide a replacement for the "bitbake PN-PV" since it is useful, for example, can we support the PREFERRED_VERSION_${PN} in the env in the future ? There is a similar bug:
If you set BB_PRESERVE_ENV=1 you can set
PREFERRED_VERSION_xxxfrom the environment so this should already be possible?It seems that the BB_PRESERVE_ENV=1 doesn't work, but we use the
BB_ENV_EXTRAWHITE, for example:
Quoted 6 lines
Quoted 4 lines
$ export BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE PREFERRED_VERSION_make" $ export PREFERRED_VERSION_make="3.81",Then it works, maybe something is wrong with the
BB_PRESERVE_ENV.It is broken, yes, I've sent out a patch to fix it. There is one other
Thanks, it worked now.
Quoted 8 lines
problem, you can't use "-" in a shell environment variable so you can't do:
PREFERRED_VERSION_make-native = xxx
which is annoying. We might want to add some kind of mangling mechanism like a double underscore translating to a dash or something...
I will update these in the bugzilla
// Robert
Quoted 7 lines
Cheers,
Richard
I've done a world build on qemux86 with:
PROVIDES_prepend = "${PN} "
it worked well.
// Robert
Quoted 57 lines · Richard Purdie
For a long time we've provided PN-PV and PN-PV-PR by tweaking PROVIDES. This looks nice at first glance however it turns out to be a bit problematic. Taking make as an example where there are two versions, 3.81 and 3.82, what should "bitbake make-3.81" do?
Currently it builds make-3.81 and make-3.82 and breaks in interesting ways. Is that a bitbake bug? Well, it certainly shouldn't try and run the build. Why is it building 3.82 though? Its due to finding a dependency on "make-dev" and then trying to figure out what provides it? The answer is "make" and the default version of "make" is 3.82.
So arguably, finding "make-3.81" should infer
PREFERRED_VERSION_make= "3.81". Doing so resolved the above problem since now "make" resolves to "make-3.81".So what about if we have Recipe A:
DEPENDS = "make-3.81"
and Recipe B:
DEPENDS = "make-3.82"That is clearly an error, easy. So finally what about if we have Recipe A:
DEPENDS = "make-3.81"
and Recipe B:
DEPENDS = "make"The first recipe infers the
PREFERRED_VERSION_make= "3.81" and then forces that version on everything else. Is that desired? Probably not in most cases, at least not silently.As mitigation, we could print a WARNING about this happening. The final part of the problem is that we can ony figure this out within bitbake itself. That means we'd have to teach bitbake about the PN-PV format of PROVIDES which is breaking the separation between bitbake and the metadata. We can't win :(.
Nobody that I know of is using or relying on this functionality so perhaps we should just remove it instead which is what this patch does. Opinions?
Signed-off-by Richard Purdie <[email protected]>---
meta/conf/bitbake.conf +1
-1@@ -253,7 +253,7 @@ DEPCHAIN_POST = "-dev -dbg" DEPENDS = "" RDEPENDS = "" PROVIDES = "" -PROVIDES_prepend = "${P} ${PF} ${PN} " +PROVIDES_prepend = "${PN} " RPROVIDES = "" MULTI_PROVIDER_WHITELIST = "virtual/libintl virtual/libintl-native virtual/nativesdk-libintl virtual/xserver virtual/update-alternatives-native virtual/update-alternatives"_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core