Live data from Hacker News

Rip: Ruby's Intelligent Packaging

hellorip.com

21–24 of 24 posts

Re: Rip: Ruby's Intelligent Packaging

#21
post #17

I like how the rip deps file is a list of canonical URLs and tag/version numbers! Question: How would I use rip to track the latest version of each dependency -- maybe one is a gem and so I want the latest gem on rubyforge, but another is a github repo + branch, and another is an obscure fork on gitorious. Is there a way that Rip can tell if there are newer versions of the libs available?

There's no support for this currently, but maybe we should introduce syntax in the .rip file? `latest` or `rip-latest` or some such?

Over in the Python world, pip supports a scheme for specifying either the package name on the main Python package index, or a combo of repo URL + name to install under. Works with SVN, hg and git repositories, IIRC, and lets you pin to specific points in the repository, which ends up being pretty useful if you want to develop against a consistent snapshot of a dependency.

Re: Rip: Ruby's Intelligent Packaging

#22

How do people deploy with walled-garden package managers like this? Do you write an LSB RPM which depends on Ruby and stuff like your local syslog and net-snmp configs, and runs "gem install rip" and "rip install whatever" for you?

To be perfectly honest, I don't make operating-system-specific packages (in Python, the language I use on a daily basis). I make standard Python distutils packages, and then anyone who has Python can install them anywhere. Folks who want to can generate RPM, extracting Windows .exe, etc., from that package.

Re: Rip: Ruby's Intelligent Packaging

#23
This actually sounds very similar to the package manager we're working on for Narwhal (http://narwhaljs.org/), currently called "Tusk". It has virtualenv-style environments, dependency resolution, installation from git repos or plain HTTP servers.

Perhaps we could collaborate to make a language-agnostic package management "standard". We can of course have implementations in our languages of choice, but things like the .rip file format, directory structure, etc could be standardized.

Re: Rip: Ruby's Intelligent Packaging

#24

This actually sounds very similar to the package manager we're working on for Narwhal ( http://narwhaljs.org/ ), currently called "Tusk". It has virtualenv-style environments, dependency resolution, installation from git repos or plain HTTP servers. Perhaps we could collaborate to make a language-agnostic package management "standard". We can of course have implementations in our languages of choice, but things like…

That would be very interesting. I was thinking about this problem for a while, and would like to participate.

What I like in rubygems is that (1) it works on the 3 major OSes, (2) it compiles code for me, if the stars are aligned in the right way, and (3) there is an open central repository.

Achieving the first 2 out of 3 would rock. 3 could happen later.

Post reply on HN