On Tue, 26 Feb 2008, Michal Marek wrote:-
David Bolt wrote:
There's no need for this with versions before 11.0, unless YaST from 11.0 is going to be backported into the earlier versions.
This was just an example...
I know. I just followed along using it, but I'll use a generic version instead of yast2.
...why such a simple scheme isn't sufficient. There's no guarantee that a future yast2-branding will have the same format that today's yast2-branding. That's why some version information is needed, be it detailed as in Stanislav's proposal or just version numbers.
Okay, how about in the main package having: Requires: package-branding %version and the sub-packages: Provides: package-branding = %version This would seem to be the easiest system to use. Initially setting it up might take some effort, but it should be fairly easy to maintain afterwards. Of course, I could be missing something obvious. It certainly wouldn't be the first time. Regards, David Bolt -- Team Acorn: http://www.distributed.net/ OGR-P2 @ ~100Mnodes RC5-72 @ ~15Mkeys SUSE 10.1 32bit | openSUSE 10.2 32bit | openSUSE 10.3 32bit | openSUSE 11.0a1 SUSE 10.1 64bit | openSUSE 10.2 64bit | openSUSE 10.3 64bit RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC | RISC OS 3.11 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org