Deployment methods

now include a source tarball, a Guix package module. a Ubuntu package address, and a debian package. Neither deployments are sufficiently tested; only their build methods have so far had the focus of attention.

On Guix

1. download and un-archive »packages-here.tar.gz«
2. guix package -L ./packages -i teco
3. tecoc
   to exit, type: »ex<ESC><ESC>«

From the tarball

1. download, un-archive »tecoc-0.0.73-6474.tar.xz«
2. ./configure && make
3. src/tecoc
   »ex<ESC><ESC>« to exit the program

To try this on Ubuntu

1. see https://launchpad.net/~glisze/+archive/ubuntu/ppa0

sudo add-apt-repository ppa:glisze/ppa0
sudo apt-get update

sudo apt-get install teco

tecoc
* 256,1ez ewa-file.txt$$
* i
Hello, there
$$
* ex$$
$ cat -A a-file.txt
Hello, there
$ 

Note: this now works on 'trusty' and others; but not all

Using the »deb« to install

1. download
2. Use dpkg to install

Notes

This source archive has also the guix package module within. However, it still refers to, and fetches the github committed sources. »Fn/package-concrete« is used to prefabricate the package module. Specifying »file://$( pwd )« instead of »https://github.com...« might allow to try local deployments; see »guix/git-fetch.scm.in« to turn towards the all local deployment direction.