From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: how to add multiple versions?
Date: Thu, 10 Feb 2011 21:21:03 +0100 [thread overview]
Message-ID: <ij1hbf$2st$1@dough.gmane.org> (raw)
In-Reply-To: <4D544652.4090709@mentor.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10-02-11 21:10, Tom Rini wrote:
> On 02/10/2011 12:24 PM, AJ ONeal wrote:
>> I've got
>>
>> nodejs-0.2.6.bb
>> and
>> nodejs-0.4.0.bb
>>
>> If I do
>> `bitbake nodejs-0.2.6`
>> it builds 0.4.0 anyway with this message
>>
>> ERROR: Multiple .bb files are due to be built which each provide nodejs
>> (/home/coolaj86/overo-oe/org.openembedded.dev/recipes/nodejs/nodejs_0.2.6.bb/home/coolaj86/overo-oe/org.openembedded.dev/recipes/nodejs/
>>
>> nodejs_0.4.0.bb).
>> This usually means one provides something the other doesn't and should
>>
>> How do I make the file such that it knows one is different from the
>> other?
>>
>> There's api breakage, so current users may want to continue using the
>> 0.2.x
>> branch. I don't want to remove that in favor of 0.4.0 quite yet.
>
> There's a few ways to do this. The first is to just put D_P = -1 on the
> new version and let distros opt to upgrade everything at once. The
> second is to play virtual games like we do for libusb. The first option
> is easier to implement than the second and depending on how wide spread
> the usage is might be the best route.
Or go the libsoup route and make them parallel installable
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFNVEiuMkyGM64RGpERAmU5AJsH+WKJ9pQPaURH9SDCR964XH76VwCgl3cP
uhnNtfANhgsPApUna1H+NqE=
=GIAM
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2011-02-10 20:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 19:24 how to add multiple versions? AJ ONeal
2011-02-10 20:10 ` Tom Rini
2011-02-10 20:21 ` Koen Kooi [this message]
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='ij1hbf$2st$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.