Git package is always installed by default

[ChrisLundquist]

Earlier in the same run the git::source recipe ran ( I needed 1.8.0 + which wasn't available via yum )

       [2013-01-04T23:50:16+00:00] INFO: remote_file[/tmp/vagrant-chef-1/git-1.8.0.2.tar.gz] updated
       [2013-01-04T23:50:16+00:00] INFO: remote_file[/tmp/vagrant-chef-1/git-1.8.0.2.tar.gz] mode changed to 644
       [2013-01-04T23:50:16+00:00] INFO: Processing execute[Extracting and Building Git 1.8.0.2 from Source] action run (git::source line 40)
       [2013-01-04T23:51:15+00:00] INFO: execute[Extracting and Building Git 1.8.0.2 from Source] ran successfully

Later the package was installed via yum. Git should be in the path at this point.

       [2013-01-04T23:52:53+00:00] INFO: Processing package[curl] action install (ruby_build::default line 34)
       [2013-01-04T23:52:53+00:00] INFO: Processing package[git] action install (ruby_build::default line 34)
       [2013-01-04T23:52:53+00:00] INFO: package[git] installing git-1.7.1-2.el6_0.1 from base repository
       [2013-01-04T23:53:00+00:00] INFO: Processing execute[Install ruby-build] action nothing (ruby_build::default line 38)
       [2013-01-04T23:53:00+00:00] INFO: Processing directory[/tmp/vagrant-chef-1] action create (ruby_build::default line 48)

Here we see both installs of git

[vagrant@web-centos6 ~]$ ls -la /usr/bin/git
-rwxr-xr-x 105 root root 1138048 Jun 25  2011 /usr/bin/git
[vagrant@web-centos6 ~]$  /usr/bin/git --version
git version 1.7.1
[vagrant@web-centos6 ~]$ which git
/usr/local/bin/git
[vagrant@web-centos6 ~]$ git --version
git version 1.8.0

[ChrisLundquist]

what would be better?

Something like

package "git" do
  not_if "command -v git" # It may have been installed by source
end

or depending on the opscode recipe?

maybe

include_recipe "git"

or we could search the run list for a "git" cookbook and not install it if we find it?

[fnichol]

This should get the job done!

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.