From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] Handling of virtual/* namespace in packages
Date: Mon, 15 Oct 2007 20:33:22 +0100 [thread overview]
Message-ID: <1192476802.25543.95.camel@localhost.localdomain> (raw)
In-Reply-To: <74d0deb30710150735i2ff97bedwbbde3901a78cd6f5@mail.gmail.com>
On Mon, 2007-10-15 at 16:35 +0200, pHilipp Zabel wrote:
> You propose to add mangle
> "Depends: virtual/u-a" into "Depends: u-a-cworth"
> in the package control file in package.bbclass if there is
> PREFERRED_PROVIDER_virtual/u-a = "u-a-cworth" set?
>
> I don't think that's such a good idea, generally, as suddenly a package that
> should work with any virtual/u-a can only be installed with u-a-cworth.
We have a problem already here with ipkg and friends as I don't know how
you tell them to prefer one provider over another when you have multiple
providers. At the very least we don't currently do this and we should if
its possible. Having "virtual/u-a" in the Depends will break since the
virtual/ namespace is supposed to be for DEPENDS only, not RDEPENDS as
RDEPENDS can't cope with the choice :-( (or the '/' character in
debian's case).
There is also a bug in ipkg since it will error out if you have a arm5te
package which provides update-alternatives and depends perl, an armv4t
package which also provides it but doesn't depend on perl and no perl
armv4t package exists (armv5te isn't listed as a valid arch).
> Maybe this mangling could be done for distro specific task packages only?
PREFERRED_PROVIDER is usually distro specific config so the choices
would be elected by the distro.
Cheers,
Richard
next prev parent reply other threads:[~2007-10-15 19:39 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 [this message]
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
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=1192476802.25543.95.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.