[RFC] adding CONFLICTS

[RFC] adding CONFLICTS

[Koen Kooi]

-----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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHIhblMkyGM64RGpERAvhLAKCJPRgKuIJxnXAqfp3SX2iAJcUH1gCdH4tG
p023LyKjTM1Ac4hdoc3A8Dk=
=TFxP
-----END PGP SIGNATURE-----

Re: [RFC] adding CONFLICTS

[Graeme Gregory]

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

Re: [RFC] adding CONFLICTS

[David Farning]

On Thu, Nov 15, 2007 at 08:02:22AM +0000, Graeme Gregory wrote:
> 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.
>
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

Thanks
David Farning

Re: [RFC] adding CONFLICTS

[Graeme Gregory]

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

Re: [RFC] adding CONFLICTS

[Koen Kooi]

-----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-----