Re: New Ruby packaging guidelines progress
On 02/04/12 03:44 -0400, Bohuslav Kabrda wrote:
Hi guys,
here is a sumup of the last 2-hour FPC meeting, that me and Mo have attended:
- Virtual provides are going to be killed completely (e.g. new packages will now depend on
ruby-foo or rubygem-foo, rather than on ruby(foo) or rubygem(foo); no provides will be
therefore necessary, as the package name is enough for this).
I could not make it to the meeting, but I have some issue with this.
There are efforts to maintain a stable API rubygems called slimgems
[1]. They forked rubygems at the 1.3.6 version.
It provides ruby(rubygems), and probably greater than 80% can replace
Require: rubygems
with
Require: ruby(rubygems)
If this moved to ruby-rubygems, then none of the rubygem-foo would be
compatible with slimgems.
Further, for noarch ruby libraries, how will this change accommodate
jruby?
Take care,
vb
[1] https://github.com/slimgems/slimgems
Attachments:
- attachment.sig (application/pgp-signature — 198 bytes)