diff options
-rw-r--r-- | GNUmakefile | 8 | ||||
-rw-r--r-- | HACKING | 15 |
2 files changed, 23 insertions, 0 deletions
diff --git a/GNUmakefile b/GNUmakefile index 8becc89..3087082 100644 --- a/GNUmakefile +++ b/GNUmakefile @@ -227,6 +227,11 @@ verify: test `git rev-parse --verify HEAD^0` = \ `git rev-parse --verify refs/tags/v$(VERSION)^{}` +gem: $(pkggem) + +install-gem: $(pkggem) + gem install $(CURDIR)/$< + $(pkggem): manifest gem build $(rfpackage).gemspec mkdir -p pkg @@ -249,6 +254,9 @@ release: verify package $(release_notes) $(release_changes) $(rfproject) $(rfpackage) $(VERSION) $(pkggem) rubyforge add_file \ $(rfproject) $(rfpackage) $(VERSION) $(pkgtgz) +else +gem install-gem: GIT-VERSION-FILE + $(MAKE) $@ VERSION=$(GIT_VERSION) endif .PHONY: .FORCE-GIT-VERSION-FILE doc $(T) $(slow_tests) manifest man @@ -96,3 +96,18 @@ We will adhere to mostly the same conventions for patch submissions as git itself. See the Documentation/SubmittingPatches document distributed with git on on patch submission guidelines to follow. Just don't email the git mailing list or maintainer with Unicorn patches :) + +== Running Development Versions + +It is easy to install the contents of your git working directory: + +Via RubyGems (RubyGems 1.3.5+ recommended for prerelease versions): + + make install-gem + +Without RubyGems (via setup.rb): + + make install + +It is not at all recommended to mix a RubyGems installation with an +installation done without RubyGems, however. |