Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Hongxu Jia <hongxu.jia@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/4] pointercal-xinput: add the missing ALLOW_EMPTY
Date: Fri, 7 Nov 2014 15:43:39 +0100	[thread overview]
Message-ID: <20141107144339.GG2444@jama> (raw)
In-Reply-To: <cd8ac315e533592e4ca82994049bf3dd7c2bd6c4.1415346812.git.hongxu.jia@windriver.com>

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

On Fri, Nov 07, 2014 at 03:57:03PM +0800, Hongxu Jia wrote:
> Since the do_install conditionally install file if it has a contents,
> it should allow the package empty.
> 
> It avoids the do_rootfs failure while IMAGE_INSTALL += "pointercal-xinput"

It was removed intentionally

http://git.openembedded.org/meta-openembedded/commit/?id=9477e53e8a8ffde17b558ac436550687db4b86a0

> [YOCTO #6937]
> 
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---
>  meta/recipes-graphics/xinput-calibrator/pointercal-xinput_0.0.bb | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/meta/recipes-graphics/xinput-calibrator/pointercal-xinput_0.0.bb b/meta/recipes-graphics/xinput-calibrator/pointercal-xinput_0.0.bb
> index 65348c3..ebc5155 100644
> --- a/meta/recipes-graphics/xinput-calibrator/pointercal-xinput_0.0.bb
> +++ b/meta/recipes-graphics/xinput-calibrator/pointercal-xinput_0.0.bb
> @@ -16,5 +16,6 @@ do_install() {
>      fi
>  }
>  
> +ALLOW_EMPTY_${PN} = "1"
>  PACKAGE_ARCH = "${MACHINE_ARCH}"
>  CONFFILES_${PN} = "${sysconfdir}/pointercal.xinput"
> -- 
> 1.9.1
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

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

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

  reply	other threads:[~2014-11-07 14:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07  7:57 [PATCH 0/4] fix install package "postinst-intercept pointercal-xinput oprofileui avahi" to image failed Hongxu Jia
2014-11-07  7:57 ` [PATCH 1/4] avahi.inc: use avahi-daemon as avahi's provider Hongxu Jia
2014-11-07 14:38   ` Martin Jansa
2014-11-07 14:42     ` Burton, Ross
2014-11-08  2:31       ` Hongxu Jia
2014-11-08 18:53     ` Koen Kooi
2014-11-10  2:02       ` Hongxu Jia
2014-11-10  6:42         ` Martin Jansa
2014-11-10  7:35           ` Hongxu Jia
2014-11-11  9:02             ` Koen Kooi
2014-11-11  9:19               ` Hongxu Jia
2014-11-07  7:57 ` [PATCH 2/4] oprofileui: use oprofileui-viewer as oprofileui's provider Hongxu Jia
2014-11-07 12:06   ` Burton, Ross
2014-11-07 14:47     ` Burton, Ross
2014-11-08  9:20       ` Hongxu Jia
2014-11-07  7:57 ` [PATCH 3/4] pointercal-xinput: add the missing ALLOW_EMPTY Hongxu Jia
2014-11-07 14:43   ` Martin Jansa [this message]
2014-11-07  7:57 ` [PATCH 4/4] postinst-intercept: rename recipe for nativesdk only Hongxu Jia
     [not found]   ` <CALbNGRTsV6udERwG8XBoxuoFVqeyexwM46-u1Ot__AFBD_TAUg@mail.gmail.com>
     [not found]     ` <545C826F.6050002@windriver.com>
2014-11-07  9:28       ` Andreas Müller

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=20141107144339.GG2444@jama \
    --to=martin.jansa@gmail.com \
    --cc=hongxu.jia@windriver.com \
    --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