From: Tom Walsh <tom@openhardware.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: versioning madness
Date: Wed, 11 Apr 2007 05:41:27 -0400 [thread overview]
Message-ID: <461CAD47.7050307@openhardware.net> (raw)
In-Reply-To: <461AE6FA.8010009@balister.org>
Philip Balister wrote:
> Tom,
>
> Have you looked at bb collections?
>
> http://bitbake.berlios.de/manual/ch04s02.html#id870544
>
> I think they will do what you want. You can keep separate data and
> chose which data takes priority in case of duplicate packages.
>
AH! Thank you! That is exactly what I need.
TomW
--
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net http://cyberiansoftware.com http://openzipit.org
"Windows? No thanks, I have work to do..."
----------------------------------------------------
next prev parent reply other threads:[~2007-04-11 9:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 19:23 versioning madness Tom Walsh
2007-04-03 10:01 ` Marcin Juszkiewicz
2007-04-05 13:28 ` Cliff Brake
2007-04-08 17:10 ` Leon Woestenberg
2007-04-08 22:55 ` Tom Walsh
2007-04-09 16:51 ` Tom Walsh
2007-04-09 18:38 ` Cliff Brake
2007-04-10 1:16 ` Tom Walsh
2007-04-10 1:23 ` Philip Balister
2007-04-11 9:41 ` Tom Walsh [this message]
2007-04-11 9:57 ` Leon Woestenberg
2007-04-10 13:54 ` Cliff Brake
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=461CAD47.7050307@openhardware.net \
--to=tom@openhardware.net \
--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.