* Adam Spiers
It's not any more messy than the automatic Provides: which rubygemsdeps.rb already generates, and has a number of advantages over -1_0 suffixing:
- automatically generated so no manual renaming required by packager
- doesn't pollute the Name: field with version info already in the Version: field
- eliminates confusion in the packaging policy about when to use suffixing and when not to use it
- hidden from the user (e.g. 'rpm -q rubygem-foo' always gives the user the answer they intuitively expect)
- allows multiple minor versions to co-exist on the same machine, just like bundler does
Actually, thats *exactly* how I would like RPM-packaged GEMs to behave.
- allows *optional* enabling/disabling of multiversion: - for all gems system-wide - per gem - per gem major version - per gem minor version - per Ruby version and gem - per Ruby version and gem major version - per Ruby version and gem minor version
The multiversion property is one of the main reasons I work with plain gems. I wouldn't want to disable it at all. 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