I'm having a problem with git-svn that may be related to the perl svn bindings. Even after installing new versions of subversion and git using homebrew, git-svn is using an old version of svn:
$ git svn --version
git-svn version 1.8.2.1 (svn 1.6.18)
$ svn --version
svn, version 1.7.7 (r1393599)
How do I make git-svn use the newer version of svn?
Thanks to this answer, I found a reasonable solution. I ran sudo cpan SVN::Core, which updated the svn version of git-svn:
$ git svn --version
git-svn version 1.8.2.1 (svn 1.7.3)
The native svn version was unchanged. So I'm left with two different versions of svn, but at least they are the same major version.
If using homebrew, uninstall git, update/install svn with homebrew, then reinstall git with:
brew install git --with-brewed-svn
Another way to point the svn-perl binding to a specific svn installation on your system would be to add following line to the bash profile:
export PERL5LIB=/usr/local/lib/svn-perl
The path will vary depending on the installation directory of svn-perl bindings. For e.g., WanDisco svn client installation is usually under /opt/subversion/lib/svn-perl.
I learned about this trick from here.
Related
I want to change default Eclipse Git executable location with SourceTree installed embedded Git executable.
But in eclipse where is the configuration to change git path ?
Reason I am doing this is ,Source Tree has latest Git but separate installed version is not latest (As I don't have installation right and Through Source Tree I can update Embedded version easily).
Eclipse uses EGit which relies on JGit (a java implementation of Git).
That is why you don't see a git.exe path to set. (As opposed to SourceTree, which can use an embedded or a "system" Git)
You can only specify a Git path in order for EGit to respect your Git system config.
Eclipse has its own GIT. It relay on the EGIT project .
Source tree other other hand can use internal git or System git.
You can take the git version installed by git and try to replace it (replace the EGIT git.exe)
I recommend reading this answer by #VonC as well
Using native git not jgit in Eclipse git?
The Git Source Code Mirror on GitHub (https://github.com/git/git) says that the most recent version of Git is 2.7.4. I'm using EGit 3.5.2 on Spring Tool Suite (Eclipse Luna SR1), so that version number obviously doesn't correspond to a Git version. Is there any way to trace back what version of Git this version of EGit is based off of?
I checked here, but it only maps versions of EGit to versions of Eclipse...
https://wiki.eclipse.org/EGit/FAQ#What_is_Git.3F
As you noticed, EGit does not appear to be based on a particular version of Git. The EGit documentation has the following to say:
How compatible is EGit with Git?
Some, but not all configuration options/features in Git are available in EGit/JGit. Here is a summary, not yet complete describing some of these, including notable differences. Note that the set of EGit/JGit is not based off a particular Git version.
Practically speaking, as long as you are using the most recent version of Git, you should be OK. This is because Git itself should be backwards-compatible with whatever version of Git was concurrent with the particular release of EGit which you are using. But I would not recommend the other way around, e.g. using the first release of Git from many years ago with the latest EGit plugin.
There is no correlation between EGit and Git versions. EGit uses JGit, a pure Java implementation of the Git VCS, to access repositories. JGit versions do not follow a specific Git versions either. Though JGit is relatively on par with Git, some things are missing, for example git clone -- depth. Unfortunately, a detailed comparison does not exist
I have been working with Git from the command-line for a few weeks. I am now on a project that uses Eclipse as the IDE and EGit for the Git plugin. I am worried that by installing EGit I'm going to destroy any Git configs in my existing projects (that I've been maintaining/coding directly from a terminal).
If EGit could interfere, how so (and how can I avoid this)? If not, why?
No, it doesnt interfere. EGit only works within Eclipse and is independent from a command line Git installation. Regarding the configuration EGit of course reads your existing gitconfig. But if you use a recent Git version on the command line, there shouldn't be any differences in the config.
In fact you can keep using Git on the command line for committing, pushing etc. It doesn't matter if the project is configured for EGit in Eclipse.
How to fix this problem?
Warning: EGit couldn't detect the installation path "gitPrefix" of native Git. Hence EGit can't respect system level
Git settings which might be configured in ${gitPrefix}/etc/gitconfig under the native Git installation directory.
As I suggested in "Egit installation path error", it can be linked to the absence of a Git installation (which EGit relies on for the system config path).
Install:
Git as a portable msysgit if you are on Windows: PortableGit-1.8.4-preview20130916.7z (unzip it anywhere you want, and add the C:\path\to\PortableGit-1.8.4-preview20130916\bin to the PATH environment variable)
Or Git using the latest Git Releases from a custom PPA (Personal Package Archive) if you are on Linux
In my case installation of the latest Git version helped.
Downloaded latest version from https://git-scm.com/download/win and installed it to the same directory as Git was before. Started eclipse and error message from Error log disappeared. I have Cygwin64 installed.
I'm new to Jenkins and experimenting at the moment. I use Eclipse and run Git from within Eclipse, using the Git plugin, which is described as follows: 'Eclipse Git is an Eclipse Team provider based on JGit, a pure Java implementation of the Git version control system'.
I've installed the Git plugin for Jenkins but when I go to configure it, Jenkins complains that it can't find the Git executable. That makes sense, and the obvious solution is to install it (in my case, using a Ubuntu repository - sudo apt-get install git-core). My concern is that having two installations of Git on the machine will give rise to problems - or am I being over-cautious?
It's fine to have both - since EGit is pure Java, it has nothing to do with the installed (native code) version of Git.
Problems might arise if there was a breaking change in a future version of Git, but it should be easy enough to fix by updating both installations.