From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: RFC: handling of machine/distro features stuff
Date: Fri, 17 Nov 2006 09:25:39 +0000 [thread overview]
Message-ID: <1163755540.5551.4.camel@localhost.localdomain> (raw)
In-Reply-To: <200611170101.06186.openembedded@hrw.one.pl>
On Fri, 2006-11-17 at 01:01 +0100, Marcin Juszkiewicz wrote:
> Dnia niedziela, 29 października 2006 15:28, Marcin Juszkiewicz napisał:
> > Currently OpenEmbedded use overrides based on DISTRO, MACHINE,
> > TARGET_ARCH and few others. I want to suggest start of using also
> > {MACHINE,DISTRO}_FEATURES because we have some stuff in metadata which
> > make sense only on some targets only - for example madwifi is limited
> > to PCI devices only.
>
> Holger 'zecke' Freyther pointed me to MacPorts and their 'variants'. After
> looking at them I think that those are other kind of our overrides.
>
> Which points me to this idea: how about adding COMBINED_FEATURES into
> overrides? I do not know will it slow down BitBake or make metadata bit
> more ugly but it is kind of solution.
Personally, I think its a bad idea as we have too many variables in this
field and it could end up with too much namespace pollution. We need to
keep our overrides lean :)
Also, this would automatically make any package machine specific and
make multimachine pointless (anything using COMBINED_FEATURES is machine
specific).
Richard
next prev parent reply other threads:[~2006-11-17 9:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 14:28 RFC: handling of machine/distro features stuff Marcin Juszkiewicz
2006-10-29 22:10 ` Jamie Lenehan
2006-10-30 1:32 ` Justin Patrin
2006-11-04 13:37 ` Leon Woestenberg
2006-11-17 0:01 ` Marcin Juszkiewicz
2006-11-17 9:25 ` Richard Purdie [this message]
2006-11-24 16:03 ` Marcin Juszkiewicz
2006-11-24 17:56 ` Richard Purdie
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=1163755540.5551.4.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.