News for hackers. Stuff that matters.
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.