Mailinglist Archive: zypp-devel (227 mails)

[Stephan Kulow <coolo@xxxxxxx>]

Am Montag 14 April 2008 schrieb Stanislav Brabec:
> Hallo.
>
> To provide a solution for branding packages, I need a conflict, where
> any of foo-branding-myvendor packages conflicts with any of all other
> packages with name foo-branding-*.
>
> All these packages provide the same files, but the complete list of
> packages, which will provide it, is not known in time of packaging.
>
> For example:
> gimp-branding-openSUSE will conflict with gimp-branding-SLED.
> But both have to conflict with gimp-branding-Flocke,
> gimp-branding-Flower or gimp-branding-Spring, which may be created by a
> third party. And each of them has to conflict with each another.
>
> There are two recent ideas:
>
> 1) Each of them will provide and conflict with gimp-branding
> It works in libzypp (self conflicts are ignored), but break in rpm
> level.
> [Bug 379338] weird package conflict related to kdebase4-workspace-branding
> https://bugzilla.novell.com/show_bug.cgi?id=379338
>
> 2) Do nothing. It works in rpm (file conflicts are sufficient), but does
> not work in libzypp.
>
> Is there any other solution for this problem?
make gimp-branding-X require branding-X and then add all known brandings
in the conflict list of branding-X. This is the only solution that
rpm allows ;(

and leave out all other conflicts from gimp-branding-X. The good news:
everyone learned something about rpm today ;)

Greetings, Stephan

-- 
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
-- 
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx