|
On 08/23/2017 10:07 PM, Mario Castelán
Castro wrote:
On 23/08/17 20:52, Dan Norton wrote:
Since borg is a self-contained binary, perhaps it does not need to be
formally declared as a package in Debian 8.
There is no relation between “is self-contained binary” and whether it
is in Debian. Again, borgbackup is available in Debian 8, but you have
to enable backports.
Moreover, Debian package borgbackups is not a self-contained binary. It
uses the package manager to install the dependencies, just as any other
package. It makes more sense this way when it is installed through the
package manager.
OK, following instructions for installing backports (thanks, Greg)
<https://backports.debian.org/Instructions/>
I added the following to /etc/apt/sources.list :
deb http://ftp.debian.org/debian jessie-backports main
followed by...
apt-get update
apt-get -t jessie-backports install borgbackup
and borg is installed.
By the way, I recommend to use GNU Stow
<https://www.gnu.org/software/stow/> when installing packages manually.
It makes administration much easier when several packages are installed,
and more so when upgrading or deleting packages.
The point is to keep each “package” (roughly, any program distributed
and installed as a whole; this is unrelated to packages as in apt-get)
in a directory exclusively of its own use under /usr/local/stow, or any
other directory. Then GNU Stow makes symbolic links from the directories
where the system expect the package to be (e.g.: /usr/local/bin) to the
place where the package is actually installed. This way you do not have
to remember which files belong to which package when uninstalling a
manually installed package. GNU Stow will also display a warning if you
try to install (using GNU Stow) packages that have colliding files,
instead of having them override eachother as would happen when doing
“make install”.
Oops - forgot to try GNU Stow. Another time maybe.
Thank you, Mario, for your help. Great discussion.
- Dan
|