From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Laurentiu Palcu <laurentiu.palcu@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] (image|rootfs_ipk).bbclass, rootfs.py: ipk multilib fixes
Date: Thu, 13 Feb 2014 11:38:48 +0000 [thread overview]
Message-ID: <1392291528.14081.12.camel@ted> (raw)
In-Reply-To: <20140212154001.GG10078@lpalcu-linux>
On Wed, 2014-02-12 at 17:40 +0200, Laurentiu Palcu wrote:
> On Wed, Feb 12, 2014 at 03:07:31PM +0000, Phil Blundell wrote:
> > On Wed, 2014-02-12 at 16:55 +0200, Laurentiu Palcu wrote:
> > > * /usr/lib/opkg is where the alternatives go;
> >
> > Isn't that a bug?
> I'm far from being an expert in opkg or update-alternatives, but,
> looking in /usr/bin/update-alternatives I can see:
>
> # admin dir
> ad="$OPKG_OFFLINE_ROOT/usr/lib/opkg/alternatives"
>
> Isn't that expected since the u-a provider is opkg-utils recipe?
Its certainly desirable to have one set of alternatives files on a
multilib system, not two. The variables/paths could probably do with
being better however I've prefer not to trigger autobuilder failures on
this until that gets resolved so I did take this.
Cheers,
Richard
next prev parent reply other threads:[~2014-02-13 11:39 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
2014-02-12 15:07 ` Phil Blundell
2014-02-12 15:40 ` Laurentiu Palcu
2014-02-13 11:38 ` Richard Purdie [this message]
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=1392291528.14081.12.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=laurentiu.palcu@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