I tested without, and an user can install both with, as result, a list of conflicting files. With 'Provides', the user will have this message:
Problem: the to be installed libbobcat-light-devel-static-6.02.00-8.1.x86_64 conflicts with 'libbobcat-devel' provided by the installed libbobcat-devel-6.02.00-8.1.x86_64
Solution 1: deinstallation of libbobcat-devel-6.02.00-8.1.x86_64
Solution 2: do not install libbobcat-light-devel-static-6.02.00-8.1.x86_64
I looked clearer for me. But I agree to remove all 'Provides' if you think that is better
But that should be the result of Conflicts, not the provides
provides means 'this package can be used as an alternative' - which is not really what we want: the light shall not be used as an alternative in normal cases, only for building icmake should it be valid
Not sure about the provides - this could result in packages asking for the devel to receive :light installed by zypper.
the conflicts seem sane though
I tested without, and an user can install both with, as result, a list of conflicting files. With 'Provides', the user will have this message:
Problem: the to be installed libbobcat-light-devel-static-6.02.00-8.1.x86_64 conflicts with 'libbobcat-devel' provided by the installed libbobcat-devel-6.02.00-8.1.x86_64 Solution 1: deinstallation of libbobcat-devel-6.02.00-8.1.x86_64 Solution 2: do not install libbobcat-light-devel-static-6.02.00-8.1.x86_64I looked clearer for me. But I agree to remove all 'Provides' if you think that is better
But that should be the result of Conflicts, not the provides
provides means 'this package can be used as an alternative' - which is not really what we want: the light shall not be used as an alternative in normal cases, only for building icmake should it be valid
Yes You are right, I will delete the Provides so.
Thanks :)