[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Ruby packaging in wheezy: gem2deb, new policy, etc.



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Jan 18, 2011, at 12:33 PM, Lucas Nussbaum wrote:

> Why wouldn't you want to do it with every available interpreter? That's
> what is implemented in gem2deb currently.

In an ideal world, it would be awesome if every Ruby library worked in every interpreter available. Unfortunately not all upstream developers use / test on every interpreter. For example Chef and other open source libraries by Opscode don't pass all tests on JRuby and Rubinius (possibly others). Incompatibilities between the interpreters are not encouraging.

> After what I've seen when working on gem2deb, I don't think that the
> situation is much better now. But I think that Debian could play a big
> role as a "sanitizer" for the Ruby community.


Debian is the basis of Ubuntu, and Ubuntu is a pretty heavily used Linux distribution for Cloud Computing. This drives adoption of the base platform in general, and with the popularity of Ruby on Rails, it reflects on Debian to play well with the community. I know the reputation Debian has with Ruby/Rails is not encouraging, but whos to say that can't be turned around with some simple changes, especially since they would be picked up rather quickly in Ubuntu's faster release cycle. While the Ruby/Rails community is small by comparison to other development communities, it is quite vocal, and the perception may reflect poorly, especially when the way to fix such perceived problems is relatively simple.

I'd love to see things improve, and I think the changes proposed in this thread do well to make wheezy a *very* promising release.

- -- 
Opscode, Inc
Joshua Timberman, Technical Evangelist
IRC, Skype, Twitter, Github: jtimberman

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)

iEYEARECAAYFAk02mqwACgkQO97WSdVpzT2eCgCfZaNjz8ojVpYEkGWphbVu2ooP
hX0An2TZ/CSVagtLg2+B7zvoeitFb2WI
=7U3V
-----END PGP SIGNATURE-----


Reply to: