Hi, On Tue, Feb 26, Christian Boltz wrote:
on Montag, 25. Februar 2008, Stanislav Brabec wrote: ...
Example:
Branding-enabled package:
foo.spec: Requires: foo-splash-300x400-art_foo_2_4 Requires: foo-about-strip_middle-300x300
Why not simply use foo-branding as (versioned) symbol and require / provide it? With symbols for every image, icon etc, some packages might end up with lots of symbols, which is not needed IMHO. Or do you really think some people will create branding packages which contain only parts of the package, like a package for foo-splash and another for foo-about-strip? I doubt ;-)
(some time later)
OK, got it - the problem is to make the dependencies both loose and tight enough - for example, artwork may be used for several versions of an application, but at some point in time an additional image might be added which is difficult to express as version number. [Please correct me if I'm wrong.]
While this is a valid reason, I think the solution is not doable. As example use the YaST2 theme. Currently it has about 300 icons. Nobody is able to maintain 300 Provides and Requires correct. This is impossible to do. Instead I would go the following way: yast2-branding-openSUSE provides branding version 10.2. yast2-branding-openSUSE conflicts with yast2 < 10.2 yast2 will require yast2-branding >= 10.2 On openSUSE 10.3, the branding format hasn't changed, only the color of the icons. So the version number is increased, but the provides, conflicts and requires not. Everything will continue to work, on 10.3 you can use the old or the new artwork without problems. On openSUSE 11.0, the branding needs another format. So the branding version is bumped to 11.0, the conflict is changed to yast2 < 11.0, the requires is adjusted. I'm not sure if this branding version not equal to package version will really work in this way, here I need the comments of the rpm experts. There is another reason, why I wish to see an easier dependency solution than to provide/require every singe icon: Assume somebody wishes to provide a new branding for a special product. In this way, it is possible and maintainable, to provide the complete branding in only one RPM. I know that a lot of people would not like to let their customers download a huge bunch of different RPMs. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org