How do I check out code?

Project members

        export CVS_RSH=ssh
        cvs -z3 -d :ext:<username>@common-lisp.net:/project/<project-name>/cvsroot co <module>

Or if the project uses Subversion:

        svn checkout svn+ssh://<username>@common-lisp.net/project/<project-name>/svn

To do passwordless commits read a tutorial on how to set up ssh-agent such as http://www.cs.utk.edu/~england/ssh.html

Others via anonymous checkout

There are two ways. A short one for reasonably modern cvs clients and a longish one for older cvs clients.

For reasonably modern clients:

cvs -z3 -d :pserver:anonymous:anonymous@common-lisp.net:/project/<project-name>/cvsroot co <module>

For older clients (to be tried when the above fails):

cvs -d :pserver:anonymous@common-lisp.net:/project/<project-name>/cvsroot login
  <enter anonymous as password>
cvs -z3 -d :pserver:anonymous@common-lisp.net:/project/<project-name>/cvsroot co <module>

Or if the project uses Subversion, fastest first:

       svn checkout svn://common-lisp.net/project/<project-name>/svn

	svn checkout http://svn.common-lisp.net/project/<project>/

The latter method may be less efficient, however, should help users behind proxies and firewalls.

Or if the project uses Darcs:

       darcs get http://common-lisp.net/project/<project-name>/darcs/<project-name>

top

How can I change the email address to which the nags are sent?

Please read Auto-nagging section of the the project-intro document.

top

What's wrong with LGPL?

Nothing per se, but it probably does not mean what you think it means. The highly C-centric point of view of the LGPL makes a distinction between static and dynamic linking, but tells us very little about certain issues that are of paramount importance for Lisp users:

Is loading LGPL code into a non-LGPL image ok? (runtime dependency)
Is it ok to use LGPL macros in non-LGPL code? (compile-time dependency)
Is it ok to redefine operators provided by the LGPL code in non-LGPL code?
Is it ok to distribute an image with LGPL code loaded?

Whether or not these questions are answerable within the bounds of the LGPL is a matter of debate, but given that the interpretation is not clear we do not recommend using the LGPL license for Common-lisp.net projects. If you want to disallow all of the above use GPL, and if you want to allow some or all of them use LLPGL or MIT/BSD/X11 style licenses.

top

What are the SSH fingerprints for common-lisp.net?

RSA: 17:fa:96:e3:30:7d:76:18:d0:59:2d:b5:09:41:fd:db

top

How can I connect to common-lisp.net through a restrictive firewall via ssh?

Some firewall administrators are paranoid enough to disallow outgoing connections to the ssh port, but they often allow connections to e.g. the https port. For these cases, we have SSH running on non-standard ports on shell.common-lisp.net. The https port is the most common one that is left open, but sometimes others are open, too. So ssh on shell.common-lisp.net accepts connections to ports 22 (ssh), 23 (telnet), 80 (www) and 443 (https).

To find out which ports your firewall lets through, Try to connect to the ports in order:

telnet shell.common-lisp.net 21
telnet shell.common-lisp.net 22
telnet shell.common-lisp.net 23
telnet shell.common-lisp.net 80
telnet shell.common-lisp.net 443

If a port is blocked by the firewall, you'll see something like this:

$ telnet shell.common-lisp.net 443
Trying 86.59.21.101...
telnet: Unable to connect to remote host: Connection refused

The error message may differ, depending on the firewall's configuration.

If you can connect to a port, you'll see something similar to this:

$ telnet shell.common-lisp.net 443
Trying 86.59.21.101...
Connected to shell.common-lisp.net.
Escape character is '^]'.
SSH-2.0-OpenSSH_3.8.1p1 Debian-8.sarge.4

If you found a port number that works for you, put the following segment in the ~/.ssh/config file and substitute the port that you found:

Host common-lisp.net
    Port 443   # substitute the port number you found for 443.
    HostName shell.common-lisp.net

If none of the ports on shell.common-lisp.net work for you, but you can connect to https web sites, you may be running behind a transparent https proxy. In that case, software like corkscrew (http://www.agroman.net/corkscrew/) may help you connect to common-lisp.net. top