* Adam Spiers
Stephan Kulow (coolo@suse.de) wrote:
On 06.11.2012 09:54, Klaus Kaempf wrote:
* Stephan Kulow
[Nov 06. 2012 06:43]: It's not a bug, it's a design limitation.
LOL
BTW: zypper doesn't like two packages named rubygem-foo either.
Can you please be more specific here ?
zypper is supporting multiple versions of a package (i.e. the linux kernel) for quite some time and I don't see issues with zypper and the four versions of sblim-sfcb in systemsmanagement:wbem either.
Yeah, if you configure multiversion for kernels in zypp.conf - do you want to change zypp.conf for all gems?
multiversion is not necessarily a requirement here. We are talking about a single OBS project providing the *choice* of multiple versions of a gem.
Right, thats the primary requirement. However, from a developer POV, the ability to install multiple versions of a single GEM is important when working with different Ruby/Rails projects.
AFAICS, sblim-sfcb in systemsmanagement:wbem is an example where multiversion would *not* be required, because e.g. 1.3.7 would only ever be installed on SP1 machines, and 1.3.11 on SP2 machines.
Not quite. I build sblim-sfcb in multiple versions so I can upgrade it on a e.g. SP1 machine without migrating it to SP2.
and then any product-oriented rpm could install the appropriate multiversion policy / policies into /etc/zypp/multiversion.d/
Shouldn't multiversion be the default for zypper ? Esp. since we put so much effort into shared library packaging with the ability to install multiple versions in parallel ? 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