All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-micro 2/2] sane-feed.inc: rework FEED_ARCH settings
Date: Tue, 20 Sep 2011 16:42:19 +0200	[thread overview]
Message-ID: <j5a8ob$49g$1@dough.gmane.org> (raw)
In-Reply-To: <1316529245.3510.85.camel@phil-desktop>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 20-09-11 16:34, Phil Blundell schreef:
> On Mon, 2011-09-19 at 02:20 +0400, Dmitry Eremin-Solenikov wrote:
>> Currently meta-micro's sane-feed.inc file is full of per-machine 
>> substitutions for FEED_ARCH. At best this is redundant (armv5te 
>> machines). Even worse, some settings are plain wrong (arm-oabi boxes 
>> come to mind). So instead of big per-machien table, use TUNE_PKGARCH
>> as it's done in meta-angstrom.
> 
> It's not actually obvious to me that this FEED_ARCH is serving any useful
> purpose here.  I'm inclined to just delete sane-feed.inc altogether
> unless you know a reason why it is useful to keep it.

sane-feed.inc was create by people copy/pasting from angstrom.conf without
knowing what they were doing. AFAIK, it is just dead weight nowadays,
especially in the oe-core universe.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFOeKZLMkyGM64RGpERApbSAJ0WuXKxCTtLpOeO5dWFW8xN6sItAQCfbU1+
7j9hh6yodJCfcdgEcg0o8tM=
=VXDX
-----END PGP SIGNATURE-----




  reply	other threads:[~2011-09-20 14:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-18 22:20 [meta-micro 1/2] busybox: 1.18.4 is gone, rename to 1.18.5 Dmitry Eremin-Solenikov
2011-09-18 22:20 ` [meta-micro 2/2] sane-feed.inc: rework FEED_ARCH settings Dmitry Eremin-Solenikov
2011-09-20 14:34   ` Phil Blundell
2011-09-20 14:42     ` Koen Kooi [this message]
2011-09-20 14:47       ` Phil Blundell
2011-09-21  0:52         ` Admin: Unsubscribe me please Bernard Mentink
2011-09-19 17:08 ` [meta-micro 1/2] busybox: 1.18.4 is gone, rename to 1.18.5 Phil Blundell

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='j5a8ob$49g$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --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.