All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] bash-completion: remove allarch
Date: Thu, 6 Mar 2014 20:21:22 +0100	[thread overview]
Message-ID: <20140306192122.GJ26981@jama> (raw)
In-Reply-To: <2403049.xWs40izQYL@peggleto-mobl5.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 776 bytes --]

On Thu, Mar 06, 2014 at 05:59:29PM +0000, Paul Eggleton wrote:
> On Thursday 06 March 2014 18:04:50 Martin Jansa wrote:
> > * it has runtime dependency on TUNE_PKGARCH bash, so it cannot be allarch
> 
> As we've already discussed this is not universally true. There are other ways 
> to solve this.

Like making it special case like packagegroups? That is still making me
headaches when some library (for some reason) included in packagegroup
is renamed thanks to debian.bbclass and packagegroup isn't rebuilt, so
it breaks do_rootfs..

I would rather build bash-completion only once per architecture than
rebuilding it as "allarch" every time I'm building for MACHINE with
different TUNE_PKGARCH.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2014-03-06 19:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-06 17:04 [meta-oe][PATCH] bash-completion: remove allarch Martin Jansa
2014-03-06 17:59 ` Paul Eggleton
2014-03-06 19:21   ` Martin Jansa [this message]
2014-03-07 10:09     ` [oe] " Paul Eggleton
2014-03-07 10:09       ` Paul Eggleton
2014-03-07 18:28       ` [oe] " Martin Jansa
2014-03-07 18:28         ` Martin Jansa
2014-03-15 16:01         ` [oe] " Martin Jansa
2014-03-15 16:01           ` Martin Jansa
2014-03-07  8:41 ` Matthieu CRAPET
2014-03-11 14:31   ` 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=20140306192122.GJ26981@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paul.eggleton@linux.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.