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