-
Notifications
You must be signed in to change notification settings - Fork 9
Manual installation
This installation procedure is mostly useful to create packages for operating systems that do not provide a pre-packaged version yet.
Watch this GitHub project or subscribe to the SourceForge page to receive notifications for new releases.
First make sure the dependencies are satisfied.
Change directory to a safe workspace:
$ cd ~/Desktop
Now download the main Outspline component: navigate to https://sourceforge.net/projects/outspline/files/main/ for a list of the released versions. For example, for the 0.8.4 version:
$ curl -LO http://downloads.sourceforge.net/project/outspline/main/outspline-0.8.4.tar.bz2
The main component already includes the Organism addons.
Extract the archive and change into the extracted directory:
$ tar xjf outspline-0.8.4.tar.bz2
$ cd outspline-0.8.4
Now run the setup.py
script with root privileges:
$ sudo python2 setup.py install --optimize=1
Refer to the Python documentation for more options.
The icon cache may have to be refreshed:
$ sudo gtk-update-icon-cache -q -t -f /usr/share/icons/hicolor
Outspline should now be ready to be run: see Usage for further instructions.
Navigate to https://sourceforge.net/projects/outspline/files/ for a list of the available components and versions.
When installing additional components, the procedure is similar as for the core component. For example, for outspline-extra 0.8.1:
$ curl -LO http://downloads.sourceforge.net/project/outspline/extra/outspline-extra-0.8.1.tar.bz2
$ tar xjf outspline-extra-0.8.1.tar.bz2
$ cd outspline-extra-0.8.1
$ sudo python2 setup.py install --optimize=1
Note: when creating a package for a particular package manager, the above procedure is probably run in a chroot environment; the non-core Outspline components contain files that are already provided by the core component; this means that when trying to install the generated package, it will very likely complain for conflicting files, aborting the installation. This is why, in the build instructions, you will have to delete these conflicting files after extracting the package, before moving them to the destination paths:
usr/lib/python2.7/site-packages/outspline/__init__.py{,c,o}
usr/lib/python2.7/site-packages/outspline/extensions/__init__.py{,c,o}
usr/lib/python2.7/site-packages/outspline/plugins/__init__.py{,c,o}
usr/lib/python2.7/site-packages/outspline/components/__init__.py{,c,o}
usr/lib/python2.7/site-packages/outspline/info/__init__.py{,c,o}
usr/lib/python2.7/site-packages/outspline/info/extensions/__init__.py{,c,o}
usr/lib/python2.7/site-packages/outspline/info/plugins/__init__.py{,c,o}
usr/lib/python2.7/site-packages/outspline/conf/__init__.py{,c,o}
usr/lib/python2.7/site-packages/outspline/conf/extensions/__init__.py{,c,o}
usr/lib/python2.7/site-packages/outspline/conf/plugins/__init__.py{,c,o}
usr/lib/python2.7/site-packages/outspline/dbdeps/__init__.py{,c,o}
Copyright © 2011-present Dario Giovannetti — Outspline is distributed under the terms of the GPLv3