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?
Rip: Ruby's Intelligent Packaging
21–24 of 24 posts
Re: Rip: Ruby's Intelligent Packaging
#22How 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?
Re: Rip: Ruby's Intelligent Packaging
#23Perhaps 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
#24This 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…
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.