All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
	<openembedded-devel@openembedded.org>
Subject: Re: [RFC] adding CONFLICTS
Date: Fri, 16 Nov 2007 11:14:48 +0100	[thread overview]
Message-ID: <473D6D98.9050305@student.utwente.nl> (raw)
In-Reply-To: <20071116083222.552a9c30@cimmeria>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Graeme Gregory schreef:
> 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.

It goes even a bit deeper as staging, since you want certain packages to
not get build at all. With packaged staging you can still build a feed
that is internally inconsistant, which is what the CONFLICTS is trying
to solve.

regards,

Koen


- --
koen@dominion.kabel.utwente.nl will go go away in december 2007, please
use k.kooi@student.utwente.nl instead.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHPW2YMkyGM64RGpERAm7jAKCQ2M4fjfI/eHU9RPc95RJB04YhSgCfejgP
v4/5OHK/0s0Pu8iwij54GIM=
=fUV2
-----END PGP SIGNATURE-----



      reply	other threads:[~2007-11-16 10:16 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
2007-11-16 10:14       ` 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=473D6D98.9050305@student.utwente.nl \
    --to=k.kooi@student.utwente.nl \
    --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.