Well, the Anaconda installer includes (almost) everything ObsPy needs,
so this is no rocket science, actually.
Admittedly, the conda commands have some quirks and edges, but with some
googling it is not too hard to do a completely offline installation of
obspy:
# online..
cd /tmp
wget ‘https://repo.continuum.io/archive/Anaconda2-4.3.0-Linux-x86_64.sh’
wget
‘https://anaconda.org/conda-forge/obspy/1.0.2/download/linux-64/obspy-1.0.2-py27_1.tar.bz2’
wget
‘https://anaconda.org/conda-forge/future/0.16.0/download/linux-64/future-0.16.0-py27_0.tar.bz2’
# to run tests only:
wget
‘https://anaconda.org/conda-forge/mock/2.0.0/download/linux-64/mock-2.0.0-py27_0.tar.bz2’
wget
‘https://anaconda.org/conda-forge/pbr/1.10.0/download/linux-64/pbr-1.10.0-py27_0.tar.bz2’
# offline..
$ bash Anaconda2-4.3.0-Linux-x86_64.sh
$ export PATH=/tmp/anaconda2/bin:$PATH
$ source /tmp/anaconda2/bin/activate root
(root) $ conda create --offline -n new --clone root
(root) $ source /tmp/anaconda2/bin/activate new
# to be able to run tests only (and not needed in py3):
(new) $ conda install --offline /tmp/pbr-1.10.0-py27_0.tar.bz2
(new) $ conda install --offline /tmp/mock-2.0.0-py27_0.tar.bz2
# for obspy, in general
(new) $ conda install --offline /tmp/future-0.16.0-py27_0.tar.bz2
(new) $ conda install --offline /tmp/obspy-1.0.2-py27_1.tar.bz2
(new) $ obspy-runtests
Obviously, you can come up with an infinite number of more complex
scenarios ("i want package xyz at version abc", offline updating of an
existing installation, offline updating of depencies, offline xyz, "my
conda is broken somehow.. help!?" ...), and those might be/will be
harder to tackle, but with some testing before going to
no-internet-country, it's anything but undoable.
cheers,
T
P.S.: Also, obviously, during testing such an offline installation, at
the end the obspy test suite should be run to make sure all parts of
obspy are working..
P.P.S.: I'd always strongly advise against using the root environment
for anything other than creating other environments or updating conda
command line tool itself (when necessary). Because.. if the root
environment ends up in a broken state due to an update (it has happended
for me with an update of "requests" package at some point), most conda
management commands can stop to work and things have to fixed the hard
way by tampering with files and folders (which might easily be beyond.