2013-12-16 05:51:19 +00: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
|
2013-03-20 17:40:57 +00:00
|
|
|
as if you'd installed it using a package manager.
|
2012-09-28 23:08:13 +00:00
|
|
|
|
2013-03-20 17:40:57 +00:00
|
|
|
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.
|
2012-09-28 23:08:13 +00:00
|
|
|
|
|
|
|
|
This should work on any Linux system of the appropriate architecture.
|
2013-12-16 05:51:19 +00:00
|
|
|
More or less.
|
2012-09-28 23:08:13 +00:00
|
|
|
|
|
|
|
|
|
2013-03-20 17:40:57 +00:00
|
|
|
How it works: This directory tree contains a lot of libraries and programs
|
2013-12-16 05:51:19 +00:00
|
|
|
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.
|
2012-09-28 23:08:13 +00:00
|
|
|
|
2013-12-16 05:51:19 +00:00
|
|
|
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.
|
