[meta-oe][PATCH] xpext: Allow the main package to be empty.

[meta-oe][PATCH] xpext: Allow the main package to be empty.

[Drew Moseley]

If xpext is included in a build (ie via dependency on mpv) then
builds of core-image-sato-sdk will fail with errors such as below.

Allowing the package to be empty fixes this.

     warning: Can't install mpv-dev-0.15.0-r0@i586: Can't install xpext-dev-1.0+5-r0@i586: no package provides xpext = 1.0+5-r0

Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
---
 meta-oe/recipes-multimedia/xpext/xpext_1.0-5.bb | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta-oe/recipes-multimedia/xpext/xpext_1.0-5.bb b/meta-oe/recipes-multimedia/xpext/xpext_1.0-5.bb
index d65546d..84ec5be 100644
--- a/meta-oe/recipes-multimedia/xpext/xpext_1.0-5.bb
+++ b/meta-oe/recipes-multimedia/xpext/xpext_1.0-5.bb
@@ -15,3 +15,5 @@ REQUIRED_DISTRO_FEATURES = "x11"
 
 SRC_URI[md5sum] = "1b0cb67b6f2bd7c4abef17648b062896"
 SRC_URI[sha256sum] = "a3b06f5188fd9effd0799ae31352b3cd65cb913b964e2c1a923ffa9d3c08abbe"
+
+ALLOW_EMPTY_${PN} = "1"
-- 
2.9.3

Re: [meta-oe][PATCH] xpext: Allow the main package to be empty.

[Martin Jansa]

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

On Tue, Sep 06, 2016 at 02:41:55PM -0400, Drew Moseley wrote:
> If xpext is included in a build (ie via dependency on mpv) then
> builds of core-image-sato-sdk will fail with errors such as below.
> 
> Allowing the package to be empty fixes this.
> 
>      warning: Can't install mpv-dev-0.15.0-r0@i586: Can't install xpext-dev-1.0+5-r0@i586: no package provides xpext = 1.0+5-r0

Isn't it better to disable this dependency from xpext-dev than to
install completely useless empty image into the image?

> Signed-off-by: Drew Moseley <drew_moseley@mentor.com>
> ---
>  meta-oe/recipes-multimedia/xpext/xpext_1.0-5.bb | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/meta-oe/recipes-multimedia/xpext/xpext_1.0-5.bb b/meta-oe/recipes-multimedia/xpext/xpext_1.0-5.bb
> index d65546d..84ec5be 100644
> --- a/meta-oe/recipes-multimedia/xpext/xpext_1.0-5.bb
> +++ b/meta-oe/recipes-multimedia/xpext/xpext_1.0-5.bb
> @@ -15,3 +15,5 @@ REQUIRED_DISTRO_FEATURES = "x11"
>  
>  SRC_URI[md5sum] = "1b0cb67b6f2bd7c4abef17648b062896"
>  SRC_URI[sha256sum] = "a3b06f5188fd9effd0799ae31352b3cd65cb913b964e2c1a923ffa9d3c08abbe"
> +
> +ALLOW_EMPTY_${PN} = "1"
> -- 
> 2.9.3
> 
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 169 bytes --]

Re: [meta-oe][PATCH] xpext: Allow the main package to be empty.

[Moseley, Drew]

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


> On Sep 6, 2016, at 5:06 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> 
> On Tue, Sep 06, 2016 at 02:41:55PM -0400, Drew Moseley wrote:
>> If xpext is included in a build (ie via dependency on mpv) then
>> builds of core-image-sato-sdk will fail with errors such as below.
>> 
>> Allowing the package to be empty fixes this.
>> 
>>     warning: Can't install mpv-dev-0.15.0-r0@i586: Can't install xpext-dev-1.0+5-r0@i586: no package provides xpext = 1.0+5-r0
> 
> Isn't it better to disable this dependency from xpext-dev than to
> install completely useless empty image into the image?

Probably so.  Thanks for the suggestion.  Looks like:

	http://cgit.openembedded.org/meta-openembedded/commit/?h=d523cc183903fd0bc2e53af6af99a88ea1652e0d <http://cgit.openembedded.org/meta-openembedded/commit/?h=d523cc183903fd0bc2e53af6af99a88ea1652e0d>

is probably a similar solution.  I’ll submit an update.

Drew


[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 202 bytes --]