Thorsten Kukuk wrote:
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
Yes, it looks possible, as we know lowest version compatible with the current branding, and when future version will be released, we will know the highest version not suitable for current design. I see a downside of this (and my proposal as well): Removing foo will keep foo-branding-openSUSE installed without use Maybe cyclic dependency may be OK here. (for non-bundled branding packages) -- 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: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org