All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/4] lvm2: rebase all recipes on a global lvm2.inc recipe
Date: Wed, 28 Jul 2010 15:44:38 +0200	[thread overview]
Message-ID: <20100728134438.GA20716@excalibur.local> (raw)
In-Reply-To: <4C4DE8FA.7060707@gravedo.de>

Hello.

On Mon, 2010-07-26 at 21:58, Simon Busch wrote:
> On 26.07.2010 09:46, Stefan Schmidt wrote:
> > Hello.
> > 
> > On Tue, 2010-07-20 at 20:44, Simon Busch wrote:
> >> This rebases all specific versions of lvm2 on a global recipe lvm2.inc which defines the
> >> common parameters for building lvm2. Staging is overwritten as we don't need any of the
> >> executables or manpages the build of lvm2 produces for any related builds.
> >>
> >> Signed-off-by: Simon Busch <morphis@gravedo.de>
> > 
> > Looks good. Two comments below.
> 
> Thank you for commenting this patches!
> 
> > 
> >> diff --git a/recipes/lvm2/lvm2.inc b/recipes/lvm2/lvm2.inc
> >> new file mode 100644
> >> index 0000000..a7e37b5
> >> --- /dev/null
> >> +++ b/recipes/lvm2/lvm2.inc
> >> @@ -0,0 +1,20 @@
> >> +SECTION = "utils"
> >> +DESCRIPTION = "LVM2 is a set of utilities to manage logical volumes in Linux."
> >> +LICENSE = "GPL"
> >> +DEPENDS = "device-mapper"
> >> +INC_PR = "r2"
> >> +
> >> +S = "${WORKDIR}/LVM2.${PV}"
> >> +SRC_URI = "ftp://sources.redhat.com/pub/lvm2/old/LVM2.${PV}.tgz \
> >> +           file://crosscompile_fix.patch"
> >> +
> >> +# Unset user/group to unbreak install.
> >> +EXTRA_OECONF = "--with-user= --with-group= --disable-o_direct"
> >> +EXTRA_OECONF_arm = "--with-user= --with-group= --disable-o_direct"
> > 
> > I can see that you just merged this in from an already existing recipe, but do
> > we know why we have an overrirde for ARM here which changes nothing? Looks bogus
> > to me.
> 
> Hm, you are right. I checked it with recompiling without the
> EXTRA_OECONF_arm statement. It works fine. Is it ok if I supply an extra
> patch removing this statement or should I rework this patch?

Both is fine with me.

> >> +inherit autotools
> >> +
> >> +# We don't need to stage anything (the executables are no needed at build time by any
> >> +# other recipe)
> >> +do_stage() {
> >> +}
> > 
> > While we don't need the executables the don't hurd either IMHO. Can we get rid
> > of this?
> > 
> 
> The problem was, that the executables and manpages where installed into
> the staging dir and never removed, when the packages was clean ur
> purged. So I added the empty do_stage block to avoid stage of anything
> from this package as we don't need them anyway.

Hm, this smells like a bug somewhere else. Did the staged binaries bring in
other problems or could they get staged until we find out why they are not
removed?

regards
Stefan Schmidt



  reply	other threads:[~2010-07-28 13:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 18:44 Some love for the lvm2 recipes Simon Busch
2010-07-20 18:44 ` [PATCH 1/4] lvm2: rebase all recipes on a global lvm2.inc recipe Simon Busch
2010-07-26  7:46   ` Stefan Schmidt
2010-07-26 19:58     ` Simon Busch
2010-07-28 13:44       ` Stefan Schmidt [this message]
2010-07-28 17:20         ` Simon Busch
2010-07-28 18:07           ` Stefan Schmidt
2010-08-10 15:51             ` Simon Busch
2010-08-13 21:57             ` Stefan Schmidt
2010-07-20 18:44 ` [PATCH 2/4] lvm2.inc: add patch to fix building Simon Busch
2010-07-26  7:46   ` Stefan Schmidt
2010-07-20 18:44 ` [PATCH 3/4] lvm2.inc: add machine specific configuration file Simon Busch
2010-07-26  7:46   ` Stefan Schmidt
2010-07-20 18:44 ` [PATCH 4/4] lvm2: add configuration file for palmpre machine Simon Busch
2010-07-26  7:47   ` Stefan Schmidt
2010-08-10 15:44 ` [PATCH 5/5] lvm2.inc: remove unnecessary EXTRA_OECONF_arm line from recipe Simon Busch
2010-08-13 21:55   ` Stefan Schmidt
2010-08-16 13:59     ` Stefan Schmidt
2010-08-16 17:52       ` Simon Busch

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=20100728134438.GA20716@excalibur.local \
    --to=stefan@datenfreihafen.org \
    --cc=openembedded-devel@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.