From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Cc: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel@openembedded.org>
Subject: Re: [RFC] adding CONFLICTS
Date: Thu, 15 Nov 2007 08:02:22 +0000 [thread overview]
Message-ID: <20071115080222.2c3a597f@cimmeria> (raw)
In-Reply-To: <472216E5.6060708@student.utwente.nl>
On Fri, 26 Oct 2007 18:33:41 +0200
Koen Kooi <k.kooi@student.utwente.nl> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> Since we don't have packaged staging yet, what do people thing about
> adding CONFLICTS to packages the interfere with eachother like e.g.
> medialibraries like sdl and their hacked-up qte versions, multiple
> kernels (linux-foo and linux-foo-devel) etc...
>
> regards,
>
> Koen
This sounds good in theory as long as bitbake actually chokes with
a sensible error message.
Hopefully then it makes uses more aware what went wrong.
Graeme
next prev parent reply other threads:[~2007-11-15 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 16:33 [RFC] adding CONFLICTS Koen Kooi
2007-11-15 8:02 ` Graeme Gregory [this message]
2007-11-16 1:16 ` David Farning
2007-11-16 8:32 ` Graeme Gregory
2007-11-16 10:14 ` 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=20071115080222.2c3a597f@cimmeria \
--to=dp@xora.org.uk \
--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.