From: Sebastian Spaeth <Sebastian@SSpaeth.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] task-base: Introduce DISTRO_apm and convert recipes to use it.
Date: Fri, 04 Dec 2009 08:28:43 +0100 [thread overview]
Message-ID: <4B18BA2B.40602@SSpaeth.de> (raw)
In-Reply-To: <1259911168-19992-2-git-send-email-Sebastian@SSpaeth.de>
This is my take on solving our problem that we want a different "apm"
provider. Koen outlined this solution, so this way I went.
All recipes that RDPEND on "apm" basically get a
DISTRO_apm ?= "apm"
RDEPEND += ${DISTRO_apm}
This could also be done with a virtual/apm package, and a
PREFERED_PROVIDER set to apm for all distros. Which would even be
cleaner I think, with the downside that all other distros would need to
set a prefered provider too.
For things like this is would be nice to get a common sane-providers.inc
where these standard providers can be defined.
What do you think? Can I commit this?
spaetz
next prev parent reply other threads:[~2009-12-04 7:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-04 7:19 [PATCH 1/2] shr.conf: set DISTRO_apm = fso-apm Sebastian Spaeth
2009-12-04 7:19 ` [PATCH 2/2] task-base: Introduce DISTRO_apm and convert recipes to use it Sebastian Spaeth
2009-12-04 7:28 ` Sebastian Spaeth [this message]
2009-12-04 9:14 ` Phil Blundell
2009-12-04 7:29 ` Michael 'Mickey' Lauer
2009-12-04 7:46 ` Sebastian Spaeth
2009-12-04 8:09 ` [PATCH] [UPDATED] task-base: Introduce DISTRO_APM and convert recipes to use that Sebastian Spaeth
2009-12-04 7:33 ` [PATCH 2/2] task-base: Introduce DISTRO_apm and convert recipes to use it Sebastian Spaeth
2009-12-04 8:39 ` Koen Kooi
2009-12-04 11:02 ` Sebastian Spaeth
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=4B18BA2B.40602@SSpaeth.de \
--to=sebastian@sspaeth.de \
--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.