A work in progress
Coral aims to complement and – to some extent – replace RubyGems by pulling in and organizing git repositories.
Fetching a project:
$ coral clone git://github.com/wycats/thor.git
In your code:
require 'coral' require 'thor'
-
with gems you have to wait for a release;
-
you can’t fork a gem, contribute and push;
-
publishing gems always felt dirty, admit it;
-
with git you can ride an experimental branch of your favorite project;
-
with git you have history.
Coral will help you maintain submodules.
Coral will help you deploy.
No, and – like you – I keep wondering why is that.