Alternatively, Springdale Linux (http://springdale.math.ias.edu/) has RPMs that will work on RHEL6/CentOS6. You just need git (http://springdale.math.ias.edu/data/puias/computational/6.4/x86_64/git-1.8.3.1-1.sdl6.x86_64.rpm) and perl-Git (http://springdale.math.ias.edu/data/puias/computational/6.4/x86_64/perl-Git-1.8.3.1-1.sdl6.noarch.rpm).
-- Christopher L Tubbs II http://gravatar.com/ctubbsii On Wed, Jul 17, 2013 at 9:25 AM, Keith Turner <[email protected]> wrote: > Thanks for the instructions Christopher. I had to take the additional step > of compiling git-credential-gnome-keyring. I did the following. > > git clone https://github.com/git/git.git > cd git/ > git checkout v1.8.3.3 > make > make install > cd contrib/credential/gnome-keyring > make > cp git-credential-gnome-keyring ~/bin > > I had alread cloned from apache and was committing locally. I had to > change my url in .git/config from > > https://git-wip-us.apache.org/repos/asf/accumulo.git > > to > > https://[email protected]/repos/asf/accumulo.git > > Now I am up and running with the latest git and gnome keyring is working. > > > > On Tue, Jul 16, 2013 at 10:57 PM, Christopher <[email protected]> wrote: > >> So, git is writable now. >> >> If you have a newer (>1.8.0) version of git on a Gnome-based >> distribution of Linux, you may want to consider using gnome-keyring >> for your credential helper (don't forget your username in the >> upstream/clone url for this to work; this is different from versions >> 1.7.x where you must omit your username in the url to utilize the >> ~/.netrc file with curl). This will help you avoid typing in your >> password for every push without saving it in a plaintext file: >> git config --global credential.helper gnome-keyring >> >> I went ahead and deleted the remote branches that had already been >> merged to trunk in subversion before switching, and whose changes >> already appear in master. I'm not sure if we want to do the same for >> release-candidate tags (I did delete an old test tag I had made, so it >> is possible). >> >> I also updated merged some changes I made for ACCUMULO-1030 into >> master, and it looks like the git commit notifications work fine. >> >> About the git commit notifications.... they seem to provide a separate >> notification for each commit, and all at once when you push. I'm not >> sure if we can tweak this, but as is, it seems to encourage squashing >> commits before pushing to the asf git repo. What's nice, though, is >> you also get notifications for things other than commits, like branch >> deletes. >> >> -- >> Christopher L Tubbs II >> http://gravatar.com/ctubbsii >>
