From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Mike Crowe <mac@mcrowe.com>
Subject: Re: [PATCH] e2fsprogs: Cope with ${libdir} and ${base_libdir} being the same
Date: Thu, 23 Feb 2012 20:16:56 -0800 [thread overview]
Message-ID: <4F470F38.7040502@linux.intel.com> (raw)
In-Reply-To: <1329405215-9037-1-git-send-email-mac@mcrowe.com>
On 02/16/2012 07:13 AM, Mike Crowe wrote:
> ${libdir} and ${base_libdir} may be the same. If they are don't try and
> move files onto themselves.
>
> Signed-off-by: Mike Crowe<mac@mcrowe.com>
> ---
> meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.bb | 10 ++++++----
> 1 files changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.bb b/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.bb
> index 2289211..9647e51 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"
> @@ -32,9 +32,11 @@ do_install () {
>
> do_install_append () {
> # e2initrd_helper and the pkgconfig files belong in libdir
> - install -d ${D}${libdir}
> - mv ${D}${base_libdir}/e2initrd_helper ${D}${libdir}
> - mv ${D}${base_libdir}/pkgconfig ${D}${libdir}
> + if [ ! ${D}${libdir} -ef ${D}${base_libdir} ]; then
> + install -d ${D}${libdir}
> + mv ${D}${base_libdir}/e2initrd_helper ${D}${libdir}
> + mv ${D}${base_libdir}/pkgconfig ${D}${libdir}
> + fi
> }
>
> # blkid used to be part of e2fsprogs but is useful outside, add it
Merged into OE-core
thanks
Sau!
prev parent reply other threads:[~2012-02-24 4:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 15:13 [PATCH] e2fsprogs: Cope with ${libdir} and ${base_libdir} being the same Mike Crowe
2012-02-24 4:16 ` 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=4F470F38.7040502@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=mac@mcrowe.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