header image

git_octocat.png I Don’t want to reiterate what has already been said on this topic (I ended up in the same boat - tried more tools, didn’t really like any of them and settled for giternal).

Giternal seems to work nicely - after you get the initial roadblock out of the way. According to the README, you should install giternal with

gem install giternal

then use the giternal executable to do various things.

The problem is that after installation, there is no giternal executable - the problem is that gem installs version 0.0.1, which doesn’t have it. You have to get the sources from git and set it up yourself:

git clone git://github.com/pat-maddox/giternal.git
cd giternal
sudo ruby setup.rb

and you are good to go.

Hope this saves someone a few minutes.



If you liked the article, subscribe to the feed   and follow me on twitter!.


      

4 Responses to “Git External Dependency Management with Giternal”

  1. Luis Lavena Says:

    Running setup.rb will install into your ruby installation, but not using Gems!

    Further updates of the gem could clash with the library located now into ruby lib directory, contrary to the one from the gem.

    Check if there are rake tasks for building and installing the gem from the git clone and avoid direct installation using setup.rb

    Just my suggestion.

  2. peter Says:

    @Luis:- you are right, however the provided Rakefile is empty and this probably means that there is no rake task for building the application?

  3. Jeff Jolma Says:

    Hi all.

    I ran into similar problems installing giternal and posted a solution: http://jolma.org/blog/?p=322

    Hope this helps.

    Jeff

  4. peter Says:

    @Jeff:

    Thanks, for the link - I believe yours is the right way to do it!

Leave a Reply




Bad Behavior has blocked 874 access attempts in the last 7 days.