* Adam Spiers
Klaus Kaempf (kkaempf@suse.de) wrote:
* Stephan Kulow
[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 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The 'bug' is that I need to create two different 'package' entries in OBS. I'd rather see OBS support multiple versions for a package natively.
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?
Yes, of course !
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?
It will work. But as said before, you'll need to create two different (same rubygem-foo prefix, different suffix) packages in d:l:r:e Klaus -- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org