All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] sysvinit-inittab: Fixed license warning.
Date: Mon, 19 Mar 2012 09:07:36 -0700	[thread overview]
Message-ID: <4F6759C8.5060200@linux.intel.com> (raw)
In-Reply-To: <14ba30517e7ece9590e5ea76a963ed9b6720df09.1332121842.git.lianhao.lu@intel.com>

On 03/18/2012 06:52 PM, Lianhao Lu wrote:
> WARNING: .../sysvinit-inittab-2.88dsf-r6/sysvinit-2.88dsf/COPYING could
> not be copied for some reason. It may not exist. WARN for now.
>
> Signed-off-by: Lianhao Lu<lianhao.lu@intel.com>
> ---
>   .../sysvinit/sysvinit-inittab_2.88dsf.bb           |    6 +++++-
>   1 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb b/meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb
> index 3a716d7..85e34c8 100644
> --- a/meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb
> +++ b/meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb
> @@ -11,7 +11,11 @@ S = "${WORKDIR}/sysvinit-${PV}"
>
>   INHIBIT_DEFAULT_DEPS = "1"
>
> -do_configure() {
> +do_unpack_append() {
> +	bb.build.exec_func('do_copy_lic', d)
> +}
> +
I think it would be better to do the copy in a do_configure_prepend() Or 
can we set ${S} to ${WORKDIR} and not have to copy it at all?


> +do_copy_lic () {
>   	cp ${WORKDIR}/COPYING ${S}/
>   }
>



  reply	other threads:[~2012-03-19 16:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19  1:52 [PATCH 0/1] warning fix of sysvinit-inittab Lianhao Lu
2012-03-19  1:52 ` [PATCH 1/1] sysvinit-inittab: Fixed license warning Lianhao Lu
2012-03-19 16:07   ` Saul Wold [this message]
2012-03-20  0:44     ` Richard Purdie

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=4F6759C8.5060200@linux.intel.com \
    --to=sgw@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.