Once Lino is installed, you can always download the latest snapshot to get the latest fixes. This is currently the only method since it is too early to work with official releases.
First-time installation
- checkout to /var/snapshots/lino
from anonymous SVN
mkdir /var/snapshots mkdir /var/snapshots/lino cd /var/snapshots/lino svn checkout svn://svn.berlios.de/lino/trunk
- Add lino to your Python path:
Edit your file /usr/local/lib/python2.3/site-packages/sitecustomize.py:
import site site.addsitedir("/var/snapshots/lino/trunk/src") #from lino.console import sitecustomize - Create the 'lino' launcher script:
echo 'python -c "import lino.runscript" $*' > /usr/local/bin/lino chmod a+x /usr/local/bin/lino
- run the test suite:
cd /var/snapshots/lino/trunk/tests lino runtests
Updating your Lino to the most recent version
Note: if you have a Lino installation which you actually use, then don't do the following without the explicit advice of your Lino export.
Go to the directory containing your local copy and type the command:
cd /var/snapshots/lino/trunk svn update
Configuring your SVN client on Windows
Because your Python will probably create *.pyc files in your local work copy, you should tell SVN to ignore them. Here is how to do it:
cd %APPDATA%\Subversion edit config
[miscellany] ### Set global-ignores to a set of whitespace-delimited globs ### which Subversion will ignore in its 'status' output, and ### while importing or adding files and directories. global-ignores = *.o *.lo *.la #*# .*.rej *.rej .*~*~.#* .DS_Store *.pyc
Refering articles:
- not yet ready to run on a stable Debian (Problem reports 02.02.06) — Lino is not yet ready to run on a stable Debian. The article Using an SVN snapshot is not yet true...