News for hackers. Stuff that matters.
Re:Giving up on Ruby packaging by tptacek on Sunday January 02, 2011 @02:40PM (#2060797)
Can I be the jerk on this thread to raise my hand and say, "from what I can see, every single thing Debian has done with Ruby, from the way they split Ruby up into separate packages to the mindboggling damage they inflicted on RubyGems, has worked to the detriment of Ruby and provided no discernable benefit to end-users"?

For at least a year now, I've simply accepted that Debian's Ruby lives in a parallel bizarro-universe, rm'd any trace of it that intrudes on my own (real) universe, and installed everything from source.

I write this not to feel better about myself but to attract the passionate, angry disagreements that will help me better understand the problems this guy was trying to solve, so I can understand how he looks at the world and what his decision means instead of silently hoping that this post means nobody is going to try to integrate Debian and Ruby anymore.

Re:Giving up on Ruby packaging by bryanlarsen on Sunday January 02, 2011 @02:58PM (#2060841)
You've done the right thing, but attributed blame in the wrong place, it's Ruby that's in the parallel bizarro-universe.

Ruby, RVM, ruby-gems etc were all designed and built for developers. APT was designed and built for system administrators.

In the world of system administrators, API differences between versions 2.3.5 and 2.3.8 would be considered bugs. In the world of Ruby/Rails, that's just standard practice. APT would not let you install both 2.3.5 and 2.3.8 simultaneously because that would be silly. It is silly, but it's useful for developers. The detriments are obvious to everybody but the Ruby community -- DLL hell is one of the major factors in the decline of the Windows platform.

So yes, keep Ruby off in it's own parallel universe, partitioned off using RVM or bundler. As a developer, this brings you many real benefits. But recognize the real detriments to normal users and system administrators, and place the blame squarely where it belongs -- on the Ruby community.

Re:Giving up on Ruby packaging by tptacek on Sunday January 02, 2011 @03:01PM (#2060846)
Ruby is overwhelmingly used by developers. I understand that there are a few projects that are so popular and useful that end-users and admins might want to install them without actively developing for them. But the decision to optimize Ruby for that use case, instead of for its overwhelmingly more common use case as "developer tool", just - seems - wrong.

I don't "blame" anyone. I think Debian is wrong about Ruby.

Re:Giving up on Ruby packaging by bryanlarsen on Sunday January 02, 2011 @03:09PM (#2060867)
But is that a coincidence? Python is widely used by end users -- a large portion of the Ubuntu apps are written in Python. Ruby is widely used by end users via the web (zillions of twitter users, for example), but it is not widely used for desktop apps, even though it would be a good language for them.
Re:Giving up on Ruby packaging by tptacek on Sunday January 02, 2011 @03:19PM (#2060890)
It wasn't Debian's place to decide that maybe Ruby should work more like Python. Packaging, by the way, is a longstanding sore point with Python developers; RubyGems is one of the few clear wins Ruby had over Python.
Re:Giving up on Ruby packaging by thristian on Sunday January 02, 2011 @09:25PM (#2061852)
Really? I haven't used RubyGems, but one of my favourite things about Python packaging is that I can take a proper Python distutils-based package, and in about thirty seconds create a usable RedHat package that my sysadmin colleagues can safely and easily deploy to our production systems, alongside all the other updates they manage.

I believe various Debian packaging "helper" scripts (like Joey Hess' "debhelper") have built-in support for Python distutils packages too.

Re:Giving up on Ruby packaging by bad_user on Monday January 03, 2011 @12:21PM (#2063834)
Python's index is the equivalent of rubygems.org. "pip" / "easy_install" is the equivalent of the "gem" command. "virtualenv" is the equivalent of "rvm" (more or less, I prefer virtualenv), a gem in Python's world is a package containing a "distutils" specification.

The difference: python's index is more comprehensive and CPAN still beats both :)

Re:Giving up on Ruby packaging by lusis on Sunday January 02, 2011 @04:46PM (#2061165)
And look where Python is on the various distributions. Behind. Constantly behind. The day a distro decides to use Ruby for system level stuff like they used python is the day that Ruby on that distro is DoA.
Re:Giving up on Ruby packaging by bryanlarsen on Sunday January 02, 2011 @05:13PM (#2061259)
Of course it's behind, and that's what end users want. Bleeding edge is called that for a reason.

Python on Debian works fine. There are a whole bunch of apps written in old versions of Python that just work, and you never have to fiddle with dependencies, and you never break them.

If you want to develop in Python, you install virtualenv and you get a bleeding edge setup exactly like you want it, and it doesn't break your working apps.

Re:Giving up on Ruby packaging by lusis on Tuesday January 04, 2011 @12:20PM (#2067674)
I'm not talking about local development. I'm talking about getting the running code on the server and deployed.

Want to run X ruby gem or Y python module in your codebase? Better hope it works with the antiquated version of python or ruby on the OS.

Re:Giving up on Ruby packaging by regularfry on Tuesday January 04, 2011 @05:10PM (#2068744)
So don't do that, then.

The OS-packaged Python version is designed to support the OS-packaged Python applications. No more, no less. The whole point of having a software distribution is that it's curated such that it all works together. Your code? Not curated, so no guarantees. Module Y? Maybe curated, maybe not.

Getting "running code on the server" is an edge case, not the primary goal.

Re:Giving up on Ruby packaging by cdavid on Monday January 03, 2011 @09:12PM (#2065567)
You say that as if that's a bad point: what's the point of being always on the bleeding edge for the end user ? What do you think is the work of a linux distribution (or any packager, really). I am quite proeficient in python (which has basically the same issue), and certainly can compile it by myself - but this takes time, knowledge, and is detrimental to the platform in the end if that's required. There is no hard issue that I cannot solve by myself, but OTOH, as soon as I want to share things with other people, this is nightmarish because of versions issues, incompatibilities, etc...

Lots of people use python but are not developers at core, and having constantly changing things every few months is horrible. Imagine what would happen if everybody was working the same way: gcc in debian would be optimized for gcc developers, so you are always on the bleeding edge, and if your program crashes because gcc had a bug or temporary incompatibiliy, no biggie, right ? Same for kernel, etc...

The kernel is actually a good example on how to do things: the kernel itself changes quickly, but distros do the work of stabilizing things.

Re:Giving up on Ruby packaging by pgroves on Sunday January 02, 2011 @04:43PM (#2061152)
I agree wholeheartedly. I develop in ruby and ocaml on ubuntu, which both suffer this problem (I assume all languages do). As a user, I have no tolerance for dealing with dependency hell for things like a desktop pdf viewer or rss reader, and a decent gui frontend to APT literally provides a one-click solution to installing an application and all it's required dependencies. As a developer, I gave up on using APT as part of my development process long ago - I manage my own library of sources and binaries. It's just too painful to synchronize a development environment with the debian/ubuntu repositories that are being updated on their own schedule. From personal experience, I can say the worst case is having your development environment break b/c you updated your email client, which is easy to do if you use APT to manage your binaries, regardless of the languages involved.
Re:Giving up on Ruby packaging by davidw on Sunday January 02, 2011 @05:30PM (#2061324)
I am not going to say that the current packaging scheme is ideal, but to say that Ruby shouldn't be packaged at all on systems like Debian and Redhat is to ignore a lot of the very real good that has come of quality package managers like dpkg/apt and rpm.

One use case would be if someone, say a sysadmin, wants a good bug tracking system for internal use at their company.

    apt-get install redmine
Fetches Rails, Ruby and so on, and sets it up in a default, reasonably secure way (as far as I know, I haven't the Debian version myself).

That sort of thing is pretty commonplace with PHP web applications under Debian and Ubuntu. Granted, if you're going to hack on and modify the application in question, yeah, you may want to get it and install it yourself, but when things work well, a good packaging system lets you install and work with code that perhaps you do not know intimately.

I think you're making the mistake of viewing the world exclusively from the point of view of a Ruby developer. What would happen if you had to deal with different systems to install, maintain and upgrade the Linux kernel, Apache, Postgres, Sqlite, Ruby, GCC, Perl, Python, Gnome, and various submodules used by them? There are times when it's necessary to install your own version of something, but it's awfully, awfully nice that you can "choose your battles", and really only do that with stuff you care about and follow closely.

Sounds like Linux in the days when you installed Slackware and then just upgraded stuff by randomly recompiling bits and pieces every now and then.

BTW, I would hope that we could skip any "angry disagreements" here. Passion will do more than suffice!

Re:Giving up on Ruby packaging by erikpukinskis on Monday January 03, 2011 @04:35AM (#2062684)
I don't think that really makes sense. I think the sysadmin should instead have to do:

    apt-get install rubygems
    gem install redmine
I know it's two steps and they have to understand the dependency, but the truth is everyone in the Ruby world kind of assumes you're using Rubygems, and repackaging things from one packaging format to another just seems like it's asking for trouble.

Sysadmins can learn that if they want something from the ruby world they have to install rubygems.

Re:Giving up on Ruby packaging by regularfry on Monday January 03, 2011 @05:33AM (#2062760)
That way lies madness. Consider:

  * "Sysadmins can learn that if they want something from the Python world they have to install pip."
  * "Sysadmins can learn that if they want something from the Lisp world they have to install clbuild."
  * "Sysadmins can learn that if they want something from the Lua world they have to install luarocks."
  * "Sysadmins can learn that if they want something from the PHP world they have to install PEAR."
  * "Sysadmins can learn that if they want something from the Perl world they have to install CPAN."
  * "Sysadmins can learn that if they want something from the Haskell world they have to install cabal."
  * "Sysadmins can learn that if they want something from the O'Caml world they have to install godi."
Re:Giving up on Ruby packaging by halostatue on Monday January 03, 2011 @07:34AM (#2062932)
Why can't "apt-get install redmine" do what you suggest behind the scenes?
Re:Giving up on Ruby packaging by logic on Monday January 03, 2011 @11:24AM (#2063588)
Speaking as a system administrator, "yum install trac" works as I expect.
Re:Giving up on Ruby packaging by halostatue on Sunday January 02, 2011 @02:48PM (#2060819)
Thank you. As a Ruby package developer, I have to care about MANY platforms, not just Debian.

This is why RubyGems was developed, because neither Windows nor Mac OS X have package managers built in. Debian maintainers may despise RubyGems and what it represents, but the RubyGems developers have never been unwilling to take patches that make them better citizens. They have not, however, been interested in neutering fundamental features.

Re:Giving up on Ruby packaging by bryanlarsen on Sunday January 02, 2011 @03:05PM (#2060859)
That argument would make sense if RubyGems was actually useful on OS X or Windows. But every single application targeted at "normal users" on Windows or OSX written in Ruby bundles all dependencies, usually even including Ruby itself.

RubyGems needs to REMOVE harmful features, like the ability to install multiple minor versions of the same gem. Developers should be using RVM to get this capability.

Re:Giving up on Ruby packaging by lusis on Sunday January 02, 2011 @04:43PM (#2061153)
The ability to install multiple versions of the same gem are pretty much key to the migration path of any ruby app. Just because it doesn't fit in the package manager world of some (read: all) distributions is not the fault of Ruby.

I can't count the number of times that we rolled out (while I was at the AJC) a new version of one of our apps on a different version of rails while keeping the other apps collocated on the same box running the previous version.

Re:Giving up on Ruby packaging by fanf2 on Monday January 03, 2011 @07:33AM (#2062930)
The lack of support for multiple installed versions of the same package is a major failure of dpkg and rpm.

Have a look at NixOS for a different approach to the problem.

Re:Giving up on Ruby packaging by halostatue on Sunday January 02, 2011 @08:06PM (#2061687)
I developed PDF::Writer entirely on Windows and used RubyGems extensively. With the new Ruby Installer work by Luis Lavena and others, RubyGems is now amazingly awesome on Windows.

The Linuxes are the least-well represented and the least interested in working with RubyGems developers. There are hooks to make things work better: they were first offered by Apple and subsequently modified by Eric Hodel to be more generic so that Debian could benefit. They refused to use these vendor hooks.

You're right that apps that target "desktop" users bundle Ruby, but I remember a game from 2001 that bundled Python. This is no different. Apps need to control their dependencies (my company's backup app includes vendor-locked versions of OpenSSL in the program directory because we can't trust full compatibility without that)

Edited to add:

The RubyGems multiple version feature (which is one of the things that the Debian team seems to dislike) doesn't assign any meaning to version levels. The fact that 1.2.3 usually means "major version 1, minor version 2, patch version 3" is entirely social and of no meaning to RubyGems. The only thing that it cares about is that version A is comparably larger or smaller than version B. I could have version 1.2.3.4.5 and 1.3.5.7 and it would only care that the latter is larger (because the second level of the latter is larger than the second level of the former).

Removing this but keeping "top-level" versions would encourage people to rev their top-level versions more often. This may not be a bad thing, but it won't give you the effect you think it will.

Re:Giving up on Ruby packaging by tptacek on Sunday January 02, 2011 @03:21PM (#2060900)
Huh? OS X is my primary development platform, Debian is my primary deployment platform, and on both, I use a ruby from /usr/local/bin, and I type "bundle install" to get my deps working, and everything works fine.
Re:Giving up on Ruby packaging by bryanlarsen on Sunday January 02, 2011 @03:35PM (#2060939)
But you're a web developer. Ruby works excellently for developers and for web apps.

Debian's primary concern is for end users, those who install applications via the pretty GUI. RubyGems made some choices that are very poor for these users.

The Ruby community has decided that these users are unimportant. And that's fair, there aren't many of them. "Fixing" RubyGems would not help developers, would not help web apps, would not help OS X or Windows end users, all of whom far outnumber Linux end users.

But recognize that this is a deliberate decision on the part of the Ruby community to ignore these users. But these Linux end users are Debian's raison d'etre, so recognize that the blame properly belongs on the shoulders of the Ruby community.

It may be a reasonable decision on the Ruby community's part, but it's still their "fault".

Re:Giving up on Ruby packaging by tptacek on Sunday January 02, 2011 @03:42PM (#2060968)
I feel like we may be talking past each other.

I take your point: Ruby has made decisions that make it hard to install end-user applications (what few there are) without bundling up an entire additional Ruby universe. Ruby - community - Ruby doesn't work for end-user applications that want to depend on a single system Ruby. Yes. This is true. I get it.

But the actions Debian took to try to fix that situation broke Ruby for Ruby's real users, which are developers. You say that nothing Debian could have done would change things for developers, but that's not true; you presume that, had Debian not undertaken it's strange neutering of RubyGems, Ruby devs would still have to rebuild the universe to deploy there. No. I don't do that on OS X. I only have to do it on Debian, because Debian was wrong about Ruby.

Re:Giving up on Ruby packaging by jamtur01 on Sunday January 02, 2011 @04:22PM (#2061083)
The statement "Ruby's real users" is telling. Ruby's real users include everyone downstream using Ruby applications: web apps, gems, tools, stand-alone apps. Some compromise needs to be made to suit all parties. Thus far it seems to me that the Debian world has been trying to make it work whilst a lot of Rubyists throw rocks from the sidelines. YMMV.
Re:Giving up on Ruby packaging by tptacek on Sunday January 02, 2011 @04:27PM (#2061092)
Yes, this is clearly what the Debian people think. But you aren't engaging with the argument, you're just hissing at it.

Again: I didn't just say "Ruby's real users are people who think like I do". I said "Ruby is used by significantly more developers than by end-users and should be optimized for its most important use case". You can disagree with that, but the onus is on your to support your argument with evidence.

Instead, you've attempted to personalize the argument. Try again.

Re:Giving up on Ruby packaging by FooBarWidget on Sunday January 02, 2011 @04:42PM (#2061149)
This. From what I've seen of the entire Debian-Ruby fiasco, your post accurately describes how Debian people talk past all the people who are complaining about Ruby on Debian.

Optimize for the largest audience!

Re:Giving up on Ruby packaging by bryanlarsen on Sunday January 02, 2011 @04:48PM (#2061172)
Ruby targets developers. I think that's wrong, but let's say you're right. It still doesn't matter. Debian targets end users. If you want a distribution that doesn't target end users, use a different distribution, like Gentoo.

But Debian is one of the best distributions because of the way it targets end users and because it never compromises.

You can't eat your cake and have it too.

Re:Giving up on Ruby packaging by tptacek on Sunday January 02, 2011 @05:05PM (#2061228)
The thing you're missing here is the privileged place "/usr/bin" has on the filesystem. It is reasonable and proper for a package to expect to install a real, unadulterated version of itself in the standard user path. You can't simply say "well, developers can just install their own version" while at the same time installing a broken version of Ruby in the standard path.

The right call would have been not to package Ruby at all.

Re:Giving up on Ruby packaging by halostatue on Sunday January 02, 2011 @09:08PM (#2061816)
I think it may even be true that distribution maintainers should look at installing the scripting languages their OS requires in different privileged places and version-locking their system scripts, as upgrading Python from 2.4 to 2.7 can break some system scripts, yet useful tools like Mercurial don't like very old versions of Python.
Re:Giving up on Ruby packaging by halostatue on Sunday January 02, 2011 @09:03PM (#2061804)
Au contraire: the Debian world has crippled RubyGems, which focusses on making Ruby packaging work everywhere, while Apple made modifications that made it work as Rubyists expect without causing problems for Apple's own needs. Eric Hodel modified this to make it easier for Linux distro maintainers to allow RubyGems to work as Rubyists expect yet not break the distro's expectations. The Debian maintainers chose not to adopt this. I don't use other distros, so I don't know whether they did or not.

What I've never personally understood is why the distro maintainers didn't embrace RubyGems. There's no reason that a .deb couldn't simply wrap a .gem and use the RubyGems infrastructure to install it into a "protected" area (preventing 'gem remove' from working, per the modifications noted above). A .gem can even be a repackaged version that includes platform-specific compiled code so that it could be distributed to machines without compilers (this is one thing that could be improved for RubyGems; allowing users to gemify a built gem for deployment purposes). I've suggested this in the past and it's been met with derision from OS maintainers. I don't understand why: as I understand it, this is what happens with BSD ports of gems.

So no, the Ruby community hasn't thrown rocks from the sidelines. We've made constructive suggestions that have been derided or ignored; so ignored, we've made our own solutions that work well for our needs.

Re:Giving up on Ruby packaging by bryanlarsen on Sunday January 02, 2011 @04:41PM (#2061148)
Some of the problems that Debian has had have been simply due to lack of manpower. AFAICT, they could have made `gem update --system` work, but that would have taken a lot of time they didn't have, so they disabled it.

And it's a thankless task. There's no way that Debian would ever compromise on anything, the Ruby community is not interested in removing features from RubyGems to accomodate Debian, and the developers are caught in the middle, being blamed for problems caused by policies they have no control over.

So of course, nobody wants to volunteer to help.

That's why when they get attacked (like I saw you doing), I jump in to defend them.

There is hope for the future -- Bundler and RVM make many of the "features" of RubyGems obsolete, IMO.

But I still disagree with your statement that Ruby's real users are developers. End users are the whole point of developers. Without end users, developers are just masturbating. It's fun, but it doesn't get anywhere.

Re:Giving up on Ruby packaging by FooBarWidget on Sunday January 02, 2011 @04:48PM (#2061171)
> There is hope for the future -- Bundler and RVM make many of the "features" of RubyGems obsolete, IMO.

What? Bundler uses RubyGems! Why do you think Gemfile is called Gemfile?

I think we're talking about two different aspects of RubyGems here:

1. The "gem install" command.

2. The RubyGems database and gem activation code.

Bundler merely replaces the first part. It uses the second part at its core. Still, it makes no sense to me that you see Bundler as "hope". It installs the same gems, just to different places now, usually project-dependent spaces. This latter results in duplication and I thought that was one of the things that Debian people despise.

> But I still disagree with your statement that Ruby's real users are developers. End users are the whole point of developers. Without end users, developers are just masturbating. It's fun, but it doesn't get anywhere.

The end users are the people using the web apps. And they don't install anything.

Even if we define "end users" as "people using Ruby apps", or to take a concrete example, "Redmine users", Debian's current packaging is still next to useless. It forces users to install their own Ruby from source just to make any modern Ruby app working.

Re:Giving up on Ruby packaging by jamtur01 on Sunday January 02, 2011 @03:05PM (#2060860)
Rubbish. Try to install a binary into a directory that isn't bin and then tell me about being better citizens.
Re:Giving up on Ruby packaging by tptacek on Sunday January 02, 2011 @03:20PM (#2060894)
Can you explain what this comment means? I literally don't understand what you're trying to say.
Re:Giving up on Ruby packaging by X-Istence on Sunday January 02, 2011 @03:31PM (#2060935)
What I believe he is complaining about is the fact that there is no way to specify an alternative installation path for binaries outside of bin.

Now, I am not sure with one either way since I don't use Ruby, and am merely interpreting the sentence above.

Re:Giving up on Ruby packaging by jamtur01 on Sunday January 02, 2011 @04:17PM (#2061069)
RubyGems only allows the installation of binary files to bin. Lots of binary files should go into sbin. This is a serious limitation with packaging.
Re:Giving up on Ruby packaging by tptacek on Sunday January 02, 2011 @04:28PM (#2061095)
If the author of the package is fine with the binaries going into bin, why do you care?
Re:Giving up on Ruby packaging by jamtur01 on Sunday January 02, 2011 @04:36PM (#2061123)
So I am going to suggest you're a developer. I am, amongst other things, a packager. Lots of platforme mandate that certain types of binaries go in certain places. This isntpossible with gems. I find this very frustrating for the gems I maintain - including Puppet for example.
Re:Giving up on Ruby packaging by tptacek on Sunday January 02, 2011 @05:09PM (#2061247)
If FHS religion means you can't put something in bin(7) if it's an admin-only tool, and the author of that tool built it in a way that only allows it to be installed in bin(7) and not sbin(7), then don't package the tool. The "alter the tool so it fits with our doctrines" approach hasn't worked.

Again, this isn't Ruby saying "Jeb's network configuration script must go in bin(7) even though he wants it to go in sbin(7)". This is "every Ruby developer writes tools that go in some variant of bin(7)", and Debian not liking that.

Which, fine. Don't like it. Just don't package them.

Re:Giving up on Ruby packaging by jamtur01 on Sunday January 02, 2011 @11:59PM (#2062150)
Don't package them isn't a solution. It's sticking your head in the sand.

Again and again in the Ruby world I see the "it works for us web developers on the x number of hosts we run". The people who use Ruby for stand-alone applications across multiple hosts are largely ignored.

I'd love to see more Ruby out there - ignoring the needs of people other than developers guarantees that'll never happen. Big shops and sys admins who run non-web applications (and even those who run Ruby/Rails web applications and find the RubyGems/Passenger/Rails/Ruby/etc/etc intra/inter version interoperability failures baffling) will look at it as a manual, difficult to package solution and find other tools written in other languages.

That'll be a real shame.

Re:Giving up on Ruby packaging by tptacek on Monday January 03, 2011 @03:42AM (#2062607)
You'd like the Ruby world to be different from what it is, and more like the Debian world. So you broke Ruby. Yes, I get it.
Re:Giving up on Ruby packaging by adamzochowski on Tuesday January 04, 2011 @06:15PM (#2068994)
isn't the definition

  /bin system binaries for all users
  /sbin system binaries for root
  /usr/bin distro binaries for all users
  /usr/sbin distro binaries for root
  /usr/local/bin binaries managed by repository, but not by distro for all users
  /usr/local/sbin binaries managed by repository, but not by distro for all root
  /opt/bin/ user compiled and installed binaries for all users
  /opt/sbin/ root compiled and installed binaries for root purposes
more or less? I would expect GEMs to follow behaviour?
Re:Giving up on Ruby packaging by fanf2 on Monday January 03, 2011 @07:43AM (#2062943)
Gratuitous differences between Debian and the upstream installation layout are REALLY ANNOYING. It breaks all sorts of online documentation and means Debian users have to deal with unnecessary compatibility bugs.
Re:Giving up on Ruby packaging by FooBarWidget on Sunday January 02, 2011 @04:51PM (#2061183)
Is there any reason why you care so much about bin-vs-sbin that would make it such a dealbreaker, other than FHS ideology? Most people I know just care whether the command works, i.e. whether it's in $PATH.
Re:Giving up on Ruby packaging by jamtur01 on Sunday January 02, 2011 @11:52PM (#2062131)
We care because our customers - big, enterprise shops with thousands of hosts they manage with packages - care.
Re:Giving up on Ruby packaging by tptacek on Sunday January 02, 2011 @11:58PM (#2062149)
They care that a specific random Ruby utility was by design installed in bin(7) and thus require that Debian specifically modifies the package so that it goes in sbin(7)? I call shenanigans.
Re:Giving up on Ruby packaging by jamtur01 on Monday January 03, 2011 @12:02AM (#2062160)
You're missing my point - it's a RubyGems issue not a Debian one. Standards matter.
Re:Giving up on Ruby packaging by halostatue on Monday January 03, 2011 @07:32AM (#2062927)
Standards matter, but differ between platforms and even distributions.

Ruby is not—and should not be—beholden to any single distro's particular oddities. Adaptable, yes; broken on other platforms because of, no.

Re:Giving up on Ruby packaging by adamzochowski on Tuesday January 04, 2011 @06:20PM (#2069007)
I think the idea is that on every OS you talk the talk. Windows uses backslashes instead of slashes. etc. You meld application to OS, not the other way around.

GEMs on Debian should follow Debian ideology, much like on windows they follow windows way.

Re:Giving up on Ruby packaging by halostatue on Sunday January 02, 2011 @09:55PM (#2061903)
I repeat: "…the RubyGems developers have never been unwilling to take patches that make them better citizens."

Code talks. Provide a patch and I'm sure they'll take it, because it's a good step forward. If you do make such a patch, you'll need to consider what should happen if the user is running "gem install" without appropriate privileges or if the user is running on a system where there's no bin/ or sbin/ differentiation (e.g., Windows).

Re:Giving up on Ruby packaging by another_ali on Sunday January 02, 2011 @02:56PM (#2060838)
maybe Ruby should get something like perlbrew http://search.cpan.org/~gugod/App-perlbrew-0.15/lib/App/perl...

this is good magic

Re:Giving up on Ruby packaging by telemachos on Sunday January 02, 2011 @03:23PM (#2060913)
Um, you're joking, right? Perlbrew itself is fine (I use and like it - I actually wrote a small Bash completion script for it[2]), but it implements only a fraction of the functionality of rvm[1]. (Rvm also precedes Perlbrew by some time, I think).

[1] http://rvm.beginrescueend.com/

[2] https://github.com/telemachus/perlbrew-bash-completion

Re:Giving up on Ruby packaging by another_ali on Sunday January 02, 2011 @03:48PM (#2060980)
ahhh, i didnt know about rvm ... just use and recommend rvm then!
Re:Giving up on Ruby packaging by steveklabnik on Sunday January 02, 2011 @04:21PM (#2061080)
That's what Rubyists do.

See the rest of the thread for the ... complaints that are raised.