What's the difference between
sudo apt-get install git-all
vs
sudo apt-get install git
Is there any advantage of installing either or all?
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It only takes a minute to sign up.
Sign up to join this communityGit-all contains all sub-packages, whilst Git only includes main components with minimal dependencies.
As stated in Git on Debian Packages, Git does for example not include
graphical user interface and revision tree visualizer, tools for interoperating with other VCS's, or a web interface..
Those are additional packages.
If you look at Git-all on Debian Packages, you see it states
all sub-packages
git-all
is that massive in storage consumption), stick with the git
package.
git git-gui gitk
, thus including a GUI, but still avoid (1) the email extension for sending patches, (2) SVN support, (3) CVS support, (4) MediaWiki remote support, (5) the web interface via Apache (!) and other things.
On my Ubuntu 17.10 x64 git-all v2.14.1 depends on:
In my case git-all installed 93 packages totalling 215 MiB with all dependencies.
So, it's up to you which packages to install..
P.S. You can get all this information, for example, from Synaptic Package Manager.
I believe running sudo apt-get install git-all
is roughly equivalent to running sudo apt-get --install-suggests install git
. The latter caused problems for me on Ubuntu 15.10. Among other packages, it tried to install git-daemon-run, which didn't work. (https://bugs.launchpad.net/ubuntu/+source/runit/+bug/1448164)
Installing git-daemon-sysvinit
first, then git
, worked better for me. git-daemon-sysvinit
replaces git-daemon-run
.
So, to finish my thought, you can install either git-all
or just git
, depending on your requirements. But git-all
has the caveat that you will need to install another package first. (git-daemon-sysvinit)