From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] (image|rootfs_ipk).bbclass, rootfs.py: ipk multilib fixes
Date: Wed, 12 Feb 2014 16:55:52 +0200 [thread overview]
Message-ID: <20140212145552.GF10078@lpalcu-linux> (raw)
In-Reply-To: <1392216272.14769.270.camel@phil-desktop.brightsign>
On Wed, Feb 12, 2014 at 02:44:32PM +0000, Phil Blundell wrote:
> On Wed, 2014-02-12 at 16:33 +0200, Laurentiu Palcu wrote:
> > diff --git a/meta/classes/rootfs_ipk.bbclass b/meta/classes/rootfs_ipk.bbclass
> > index 6d4f9fa..1887dd3 100644
> > --- a/meta/classes/rootfs_ipk.bbclass
> > +++ b/meta/classes/rootfs_ipk.bbclass
> > @@ -21,7 +21,7 @@ OPKG_POSTPROCESS_COMMANDS = ""
> >
> > OPKGLIBDIR = "${localstatedir}/lib"
> >
> > -MULTILIBRE_ALLOW_REP = "${OPKGLIBDIR}/opkg"
> > +MULTILIBRE_ALLOW_REP = "${OPKGLIBDIR}/opkg|/usr/lib/opkg"
>
> Why is that change needed? Doesn't this imply that ${OPKGLIBDIR} is
> wrong?
It's needed for the multilib sanity checks. I managed to make these
checks actually work in the new code and I had to adjust the directory
whitelist.
* ${OPKGLIBDIR}/opkg is for opkg's metadata and stuff;
* /usr/lib/opkg is where the alternatives go;
laurentiu
>
> p.
>
>
next prev parent reply other threads:[~2014-02-12 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 14:33 [PATCH 0/1] (image|rootfs_ipk).bbclass, rootfs.py: ipk multilib fixes Laurentiu Palcu
2014-02-12 14:33 ` [PATCH 1/1] " Laurentiu Palcu
2014-02-12 14:44 ` Phil Blundell
2014-02-12 14:55 ` Laurentiu Palcu [this message]
2014-02-12 15:07 ` Phil Blundell
2014-02-12 15:40 ` Laurentiu Palcu
2014-02-13 11:38 ` Richard Purdie
2014-02-14 13:15 ` Paul Barker
2014-02-14 13:20 ` Paul Barker
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=20140212145552.GF10078@lpalcu-linux \
--to=laurentiu.palcu@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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.