From: Graeme Gregory <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] adding CONFLICTS
Date: Fri, 16 Nov 2007 08:32:22 +0000 [thread overview]
Message-ID: <20071116083222.552a9c30@cimmeria> (raw)
In-Reply-To: <20071116011627.GA7192@lenovo>
On Thu, 15 Nov 2007 19:16:27 -0600
David Farning <dfarning@gmail.com> wrote:
> A good way to look at this issue is to study how Seth Vidal sovled the
> issue in YUM, Fedora's updater. It is written in python, so easy for
> BitBake developers to understand.
>
> It seems that it would add a good deal of complexity to the current
> design of bitbake.
>
> Although useful this might be an idea for bitbake 2.0
>
We already have fully working package Conflicts: working.
This is talking about staging conflicts. Or in otherwords
a work around until package staging works fully including
our already complete package conflicts handling.
Graeme
next prev parent reply other threads:[~2007-11-16 8:34 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
2007-11-16 1:16 ` David Farning
2007-11-16 8:32 ` Graeme Gregory [this message]
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=20071116083222.552a9c30@cimmeria \
--to=dp@xora.org.uk \
--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.