Klaus Kaempf (kkaempf@suse.de) wrote:
* Stephan Kulow <coolo@suse.de> [Nov 05. 2012 14:41]:
No, the suffix is only there to avoid clashes between two .rpm files. You can't have rubygem-<gem> twice in the build service.
Where can I file feature (bug ?) reports against the build service ? (SCNR!)
Then I'd advocate to keep the version suffix in the build service package name (to work around the above mentioned build service bug)
I don't understand what the bug is? It already seems to work fine in the example you cited: https://build.opensuse.org/package/view_file?file=sblim-sfcb.spec&package=sblim-sfcb-sle11-sp1&project=systemsmanagement%3Awbem https://build.opensuse.org/package/view_file?file=sblim-sfcb.spec&package=sblim-sfcb-sle11-sp2&project=systemsmanagement%3Awbem
This should then allow us to have multiple versions of the same (ruby)gem in a build service project.
Example:
d:l:r:e/rubygem-foo-1_0 (-> builds rubygem-foo-1.0) foo-1.0.gem rubygem-foo.spec rubygem-foo.changes
d:l:r:e/rubygem-foo-1_1 (-> builds rubygem-foo-1.0)
I assume you meant rubygem-foo-1.1 there?
foo-1.1.gem rubygem-foo.spec rubygem-foo.changes
Note: the version suffix is only in the build service name, not in the .spec, .changes, or .rpm file.
Isn't that exactly what you did for sblim-sfcb above? Is there a particular reason why this wouldn't work for gem packages? Confused ... again ;-) -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org