All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
	<openembedded-devel@openembedded.org>
Subject: Re: [RFC] Handling of virtual/* namespace in packages
Date: Wed, 17 Oct 2007 11:07:00 +0200	[thread overview]
Message-ID: <4715D0B4.7010401@student.utwente.nl> (raw)
In-Reply-To: <1192478818.25543.108.camel@localhost.localdomain>

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

Richard Purdie schreef:
> On Mon, 2007-10-15 at 20:11 +0200, Koen Kooi wrote:
>> Richard Purdie schreef:
>>> So perhaps we should just standardise the existing xserver behaviour
>>> into a dedicated namespace:
>>>
>>> DEPENDS = "virtual/xserver"
>>> RDEPENDS_xyz = "${VIRTUAL-RUNTIME_xserver}"
>>>
>>> and the machine.conf in this case would say
>>>
>>> PREFERRED_PROVIDER_virtual/xserver = "xserver-kdrive"
>>> VIRTUAL-RUNTIME_xserver = "xserver-kdrive-fbdev"
>> We have the ${XSERVER} var for runtime selecting it:
> 
> Indeed. So what should we use for update-alternatives,
> ${UPDATE-ALTERNATIVES} ? My point was that this is going to keep biting
> us and a dedicated namespace might make sense?

I'd say we copy the VIRTUAL-RUNTIME (note the OEDEM hyphen :) ) from poky for kdrive and
u-a. Any objections?

regards,

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

iD8DBQFHFdCzMkyGM64RGpERAjzzAJ9NO/OysPMsAvQwoTShIhPawLm1sgCginm5
qL4BSJa9aw9FMgt7p3vzChk=
=pzAm
-----END PGP SIGNATURE-----



  reply	other threads:[~2007-10-17  9:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15 12:19 [RFC] Handling of virtual/* namespace in packages Marcin Juszkiewicz
2007-10-15 14:35 ` pHilipp Zabel
2007-10-15 19:33   ` Richard Purdie
2007-10-15 14:53 ` Koen Kooi
2007-10-15 19:05   ` Richard Purdie
2007-10-15 16:10 ` Richard Purdie
2007-10-15 18:11   ` Koen Kooi
2007-10-15 20:06     ` Richard Purdie
2007-10-17  9:07       ` Koen Kooi [this message]
2007-10-17 10:47         ` Dr. Michael Lauer
2007-10-17 20:32           ` Koen Kooi

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=4715D0B4.7010401@student.utwente.nl \
    --to=k.kooi@student.utwente.nl \
    --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.