Klaus Kaempf (kkaempf@suse.de) wrote:
* Stephan Kulow <coolo@suse.de> [Oct 25. 2012 16:49]:
Am 25.10.2012 16:42, schrieb Adam Spiers:
No, these are limitations in rpm itself. As darix pointed out last year, bundler's ~> operator cannot map straightforwardly into rpm Requires expressions:
http://lists.opensuse.org/opensuse-ruby/2011-07/msg00000.html
Yeah, but that information is outdated - if you read the thread a year later: http://lists.opensuse.org/opensuse-ruby/2012-07/msg00025.html
This still doesn't explain the need to tack version numbers to RPM package names. This seems a requirement from OBS (inability to build multiple version of the same package name), not from RPM !?
Yeah I guess you're right (and as per my other mail, virtual packages of the format rubygem-foo-1_1 seem to allow mapping of the ~> operator anyway). Stupid question: does OBS require that the package name matches the .spec filename, and/or the Name: field inside the spec file? Or could you have for example $project/rubygem-foo-1.0/rubygem-foo-1.0.spec which contains Name: rubygem-foo Version: 1.0 ? If this is allowed, maybe you could have $project/rubygem-foo-1.1/rubygem-foo-1.1.spec in the same OBS project which contains Name: rubygem-foo Version: 1.1 and they would both get built? If this is not allowed, maybe the restriction could be worked around by simply putting the older versions in separate projects. A project per old gem is very heavyweight; an alternative might be devel:languages:ruby:extension devel:languages:ruby:extension:old devel:languages:ruby:extension:older devel:languages:ruby:extension:oldest or similar which is *very* ugly but would at least allow a maximum of 4 different versions of the same gem with less overhead. However that may have unwanted repercussions on dependency resolution ... Thanks, Adam -- To unsubscribe, e-mail: opensuse-ruby+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-ruby+owner@opensuse.org