Stephan Kulow wrote:
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: ... 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 ;(
One could add a list of all Novell brandings, but it would look incredibly ugly: bootsplash-branding-openSUSE: Conflicts: bootsplash-branding-SLES bootsplash-branding-SLE bootsplash-branding-SLED bootsplash-branding-upstream bootsplash-branding-SLERT bootsplash-branding-SLEPOS And we have absolutely no idea, which third party branding packages will be created.
and leave out all other conflicts from gimp-branding-X. The good news: everyone learned something about rpm today ;)
Each of these features makes my packages even more ugly than before. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.cz 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@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org