git-annex/standalone/linux/skel
Joey Hess db7fb5b8cf
avoid depending on cmp
If it was not available, the caches would get deleted unncessarily.
This should be just as fast as using it.
2020-10-06 11:27:05 -04:00
..
git Revert "Unset IFS in shell scripts in the linux standalone build and OSX app." 2020-07-24 14:33:13 -04:00
git-annex Revert "Unset IFS in shell scripts in the linux standalone build and OSX app." 2020-07-24 14:33:13 -04:00
git-annex-shell Revert "Unset IFS in shell scripts in the linux standalone build and OSX app." 2020-07-24 14:33:13 -04:00
git-annex-webapp Revert "Unset IFS in shell scripts in the linux standalone build and OSX app." 2020-07-24 14:33:13 -04:00
git-receive-pack Revert "Unset IFS in shell scripts in the linux standalone build and OSX app." 2020-07-24 14:33:13 -04:00
git-shell Revert "Unset IFS in shell scripts in the linux standalone build and OSX app." 2020-07-24 14:33:13 -04:00
git-upload-pack Revert "Unset IFS in shell scripts in the linux standalone build and OSX app." 2020-07-24 14:33:13 -04:00
README
runshell avoid depending on cmp 2020-10-06 11:27:05 -04:00

You can put this directory into your PATH, or symlink the programs in this
directory to anyplace already in your PATH, and use git-annex the same
as if you'd installed it using a package manager.

Or, you can use the runshell script in this directory to start a shell
that is configured to use git-annex and the other utilities included in
this bundle, including git, gpg, rsync, ssh, etc.

This should work on any Linux system of the appropriate architecture.
More or less.


How it works: This directory tree contains a lot of libraries and programs
that git-annex needs. But it's not a chroot. Instead, runshell sets a lot
of environment variables to cause files from here to be used, and a shim
around the binaries arranges for them to be run with the libraries in here.

It shouldn't even be dependent on the host system's glibc libraries.
All that's needed is a kernel that supports the glibc included in this
bundle.