From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] usbinit, weston-init, run-postinsts, qt-demo-init: Drop allarch
Date: Mon, 23 Jun 2014 14:39:22 +0200 [thread overview]
Message-ID: <20140623123922.GF2437@jama> (raw)
In-Reply-To: <CAJTo0LbmBrwHOdYKdeaiKzHxpCdJ5XtxTUO5CnK7yi+Rm3nUyQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
On Mon, Jun 23, 2014 at 01:12:25PM +0100, Burton, Ross wrote:
> On 19 June 2014 14:54, Paul Eggleton <paul.eggleton@linux.intel.com> wrote:
> >> * update-rc.d.bbclass now adds dependency on TUNE_PKGARCH initscripts, so
> >> these cannot be allarch
> >
> > As I've said before, I really dislike this change. The system should be made
> > to handle the situation properly instead of working around the issue.
>
> Isn't this what the abi exclude thingy is for?
Do we want to maintain list of all recipes which inherit update-rc.c in
layer.conf?
That's what I did in one of our layers and the list is rather long.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2014-06-23 12:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 11:23 [PATCH] usbinit, weston-init, run-postinsts, qt-demo-init: Drop allarch Martin Jansa
2014-06-19 13:54 ` Paul Eggleton
2014-06-19 16:39 ` Martin Jansa
2014-06-19 17:03 ` Paul Eggleton
2014-06-23 12:12 ` Burton, Ross
2014-06-23 12:39 ` Martin Jansa [this message]
2014-06-23 12:44 ` Martin Jansa
2014-07-03 16:45 ` Richard Purdie
2014-07-03 17:19 ` Avoiding getting the login prompt on the LCD at boot Ulf Samuelsson
2014-07-03 20:31 ` Burton, Ross
2014-07-03 20:36 ` Ulf Samuelsson
2014-08-11 14:09 ` [PATCH] SIGGEN_EXCLUDERECIPES_ABISAFE: add initscripts Martin Jansa
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=20140623123922.GF2437@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=ross.burton@intel.com \
/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.