* Adam Spiers
Another thing to bear in mind is that even though this is an openSUSE list, the reality is that rpm packaging of gems will in some contexts be done by SUSE employees and driven by the need for those rpms as part of the platform for a current or future SUSE product such as a release of SUSE Studio or Cloud. In that context, there *may* be more compelling reasons to have one rpm per gem than there would normally be, e.g. to conform with existing product maintenance mechanisms (security updates are the most obvious, but IIRC there are automated per-rpm licensing checks too and maybe other legalities which would probably be circumvented by shipping bundles instead). So the question is whether the additional effort in packaging is justified or not.
Well, I agree with the requirements (maintainable software) but not with the implementation (forcing everything through the RPM needle eye). How about extending zypper to cope with GEMs as well as RPMs ? 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