Openembedded Core Discussions
 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] e2fsprogs: e2initrd_helper was moved in libdir but not packaged correctly in FILES_libext2fs
Date: Fri, 24 Feb 2012 10:18:24 -0800	[thread overview]
Message-ID: <4F47D470.8080909@linux.intel.com> (raw)
In-Reply-To: <1329680734-10777-1-git-send-email-andrei@gherzan.ro>

On 02/19/2012 11:45 AM, Andrei Gherzan wrote:
> The new install path of e2initrd_helper is %{libdir}. FILES_libext2fs modified accordigly to
> avoid QA warnings.
>
> Signed-off-by: Andrei Gherzan<andrei@gherzan.ro>
> ---
>   meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.bb |    4 ++--
>   1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.bb b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.bb
> index 2289211..793393e 100644
> --- a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.bb
> +++ b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.bb
> @@ -1,6 +1,6 @@
>   require e2fsprogs.inc
>
> -PR = "r2"
> +PR = "r3"
>
>   SRC_URI += "file://fallocate.patch \
>               file://acinclude.m4"
> @@ -54,7 +54,7 @@ FILES_e2fsprogs-badblocks = "${base_sbindir}/badblocks"
>   FILES_libcomerr = "${base_libdir}/libcom_err.so.*"
>   FILES_libss = "${base_libdir}/libss.so.*"
>   FILES_libe2p = "${base_libdir}/libe2p.so.*"
> -FILES_libext2fs = "${base_libdir}/e2initrd_helper ${libdir}/libext2fs.so.*"
> +FILES_libext2fs = "${libdir}/e2initrd_helper ${libdir}/libext2fs.so.*"
>   FILES_${PN}-dev += "${datadir}/*/*.awk ${datadir}/*/*.sed ${base_libdir}/*.so"
>
>   BBCLASSEXTEND = "native"

Merged into OE-core

Thanks
	Sau!



      reply	other threads:[~2012-02-24 18:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-19 19:45 [PATCH] e2fsprogs: e2initrd_helper was moved in libdir but not packaged correctly in FILES_libext2fs Andrei Gherzan
2012-02-24 18:18 ` Saul Wold [this message]

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=4F47D470.8080909@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox