mislav / coral
- Source
- Commits
- Network (3)
- Issues (0)
- Downloads (0)
- Wiki (1)
- Graphs
-
Tree:
ca92271
commit ca922710714e1e727f440dbb43fa3ad4723e8aa1
tree a2575f399476fbcb42506f7263ecdc6d76b2852a
parent f1f780c6c71d104be39b6a9ad0aa87a19ac8541e
tree a2575f399476fbcb42506f7263ecdc6d76b2852a
parent f1f780c6c71d104be39b6a9ad0aa87a19ac8541e
coral /
| name | age | message | |
|---|---|---|---|
| |
.gitmodules | Wed Jan 28 15:00:03 -0800 2009 | |
| |
README.rdoc | Wed Jan 28 05:05:15 -0800 2009 | |
| |
bin/ | ||
| |
lib/ | ||
| |
website - fa90b79 |
README.rdoc
Coral distribution system
A work in progress
Coral aims to complement and — to some extent — replace RubyGems by pulling in and organizing git repositories.
Usage
Fetching a project:
$ coral clone git://github.com/wycats/thor.git
In your code:
require 'coral' require 'thor'
Why git instead of neatly packaged gems?
- 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.
Did git ever get you laid?
No, and — like you — I keep wondering why is that.

