Mailinglist Archive: zypp-devel (227 mails)

[Stanislav Brabec <sbrabec@xxxxxxx>]

Stefan Hundhammer wrote:
> On Tuesday 15 April 2008 09:59, Klaus Kaempf wrote:
> > Well, then how can this use-case be implemented with rpm dependency
> > semantics ?
>
> It's not pretty, but how about an intentional file conflict?

It is already there. But libzypp does not use file conflict concept
(requires very huge data).

I am not sure, whether it is possible to solve such conflict
post-mortem, i. e. after failed attempt to install, the conflict will be
added to local zypp database, solver will run once again and suggest new
solution including this conflict.

Note that it would not be sufficient to implement such conflicts to
server metadata.

Typically, this conflict will look as follows:

Repository openSUSE 11.0:
gimp-branding-openSUSE

Repository SLED 11:
gimp-branding-SLED

Repository Flocke Brand:
gimp-branding-Flocke

Repository Flocke Brand could be used for both openSUSE 11.0 and SLED
11, in both cases gimp-branding-Flocke conflicts with each
other gimp-branding-*.

-- 
Best Regards / S pozdravem,

Stanislav Brabec
software developer
---------------------------------------------------------------------
SUSE LINUX, s. r. o.                          e-mail: sbrabec@xxxxxxx
Lihovarská 1060/12           tel: +420 284 028 966, +49 911 740538747
190 00 Praha 9                                  fax: +420 284 028 951
Czech Republic                                    http://www.suse.cz/

-- 
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx