This adds the possibility to specify a different ucwctl.conf file
instead of the default /etc/ucw/ucwctl.conf.  Moreover, by default
ucwctl now reads ~/.ucw/ucwctl.conf it it exists, overriding the
values in the general /etc/ucw/ucwctl.conf, and the same happens if
the ucwctl.conf is specified via the command line option.  All command
line options override the values present in any ucwctl.conf files.
The order is the following:

  1) /etc/ucw/ucwctl.conf (if it exists)
  2) ~/.ucw/ucwctl.conf (if it exists)
  3) -u|--ucwctl-file (if specified, exit if it cannot be read)
  4) command line options

A deeper discussion is available at:

  http://common-lisp.net/pipermail/bese-devel/2006-April/001932.html
  http://common-lisp.net/pipermail/bese-devel/2006-April/001961.html

darcs-hash:46901d7f422d119b4710c4a985f22a9d093a8454

darcs-hash:4d72657af74bb53fc6f59ce8ff8da22d787049df

darcs-hash:1b0885d139bcd331b9272c13f6f604f50a35110b

Usually, a normal user (i.e. a non-root one) cannot write to /var, so
the script exit with an error with the default values.

This patch adds another check for $VARROOT: when it's empty or it's
set to the default value (/var), it checks the value of $USER and if
this is different to "root", it sets $VARROOT to $HOME/var instead.

  http://common-lisp.net/pipermail/bese-devel/2006-April/001952.html
  http://common-lisp.net/pipermail/bese-devel/2006-April/001961.html

darcs-hash:de31edb11ef38fd6402d8f71c3fcebf92e31d391

darcs-hash:53ca4898af02e7477ece04c4e997f403ebc56af8

darcs-hash:4324634471211a0f15799ac947ff6f536c67aa7f

darcs-hash:a5ec18153e47d4ed572c79baca448fb2ccafcfc7

darcs-hash:ca28d2b9398b820314209a5a3a932168ca203985

darcs-hash:15ef3f5bc33afa03852126b93743737d255eb2ea

darcs-hash:556a230b83582e2a79fba24b24a00a62a286a2c2

darcs-hash:c0c0f7d0e2bba88d5b8db45ac6a37c0b7da8f5ab

darcs-hash:9931600bbe00b6cc420a905dc1e24b56f2ab91bf

darcs-hash:057194dbc4e0eb99c7c2f66d3e46ab2689881548

darcs-hash:f322683dbdf689e2408de068328ec8503b345795

This was a stupid error of mine, because I alwasy tested with the
short -c option and not the long one.

Thank Nathan Bird to have pointed it out:

  http://common-lisp.net/pipermail/bese-devel/2006-April/001915.html

darcs-hash:744fe5c9bd40d5b038c1ad94a2f471d8618c0646

darcs-hash:3b309c285681858ff1cc3c943ae389c099eee9c0

darcs-hash:dcc02835bfe06a65523c0b5b75f3f2a1e2e03113

darcs-hash:fdabddc02a1079c33cda1b98d501ba948ecca46e

Let's me explain the new ucwctl behavior, even if the manual page is
quite self-explanatory...

1) Dependencies

- detachtty (http://www.cliki.net/detachtty), with the patches
  located here:

    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282641

  This is  what you'll find in the darcs repo located at:

    http://common-lisp.net/project/bese/repos/detachtty/

- cl-launch (http://www.cliki.net/cl-launch), but there a small
  problem with the SLIME swank when you're not using the
  common-lisp-controller, as reported here:

    http://common-lisp.net/pipermail/slime-devel/2006-March/004664.html

  Follow the thread for a possible solution.

  The `:ucw.default' system depends on cl-launch as well.

- cl-fad (http://www.cliki.net/CL-FAD), the `:ucw.config' system
  (which is used by the `:ucw.default' system) depends on it.

2) Configuration

ucwctl reads by default /etc/ucw/ucwctl.conf (a shell script) and the
settings can be overridden by command line parameters, please use
`ucwctl --help` for an explicative list.

By default, UCW reads the configuration from /etc/ucw/conf.lisp (a
lisp file).  The config file can be specified to ucwctl via the
command line option -c or --config-file.

Moreover, a different lisp file used to load up UCW can be specified
to ucwctl via the command line option -s or --start-file.  By default,
this is /etc/ucw/start.lisp.

3) Applications

Another improvement is the ability to specify a folder in which there
are all the ASDF files (or symlink to them) for the applications that
UCW should load.  By default, this folder is /etc/ucw/applications.d/
and its value can be overridden in the config file.  This behavior
coexists with the ancient one: applications can be manually specified,
as it's still the case for the *example- and the *admin-application*.

The name of an application loaded by an ASDF file, however, needs to
be shared by the ASDF file (name.asd), the package defined by the
application (:name) and the variable containing the `make-instance'
declaration (*name-application*).

4) Control UCW

The commands available are now three: start, stop or attach to a
running section.

darcs-hash:f251b6f00acf232acf4053dea6b402358091854e

Basically i kept forgetting to change the :port parameter when i
switched from the httpd backend to the mod_lisp backend. With this
change all the backend specific parameters are in the same parameter
and it's easier to see that changing ones requires you to change the
other. This also makes it easier to pass backend specific initargs
since the entire list is passed unchanged to make-backend.

darcs-hash:83e988ab59ddd871231e93223548be537c565c18

darcs-hash:9195e65675928a3a94547b86f87d76ce298082a3

darcs-hash:77a251f13bd257a87908c7f8d27b359f5a407510

darcs-hash:0f66c0be37fce402735166f24d80eda7b6c26b4d

darcs-hash:ce4289ad18a3c050c9b6cfdebd286eefe862d653

UCW's startup process may be slightly (but just slightly) less newbie
friendly, on the other hand it is far easier for people who know what
they're doing to get started.

darcs-hash:ff2b9ad470abc0649e2f958003fe22b2526b930f

Fix ucwctl's detection of detachtty and attachtty (Suggested by: Asbjørn Bjørnstad <asbjxrn@bjxrnstad.net>)

darcs-hash:4b950f12337fdfb58bca3cc89032c6139c60fd1c

darcs-hash:1ef226c9d4c6dd4fe5f815533e8d39497e6482b9

darcs-hash:d973b2eb204ef9d2460eb6029c2c6db735b8c287

darcs-hash:ffe4fe1e25e3972ff8fe7eeb0e883f00aa7b6a12

darcs-hash:8e0d181ef34a9362d9dce3874b860baf2875ae56

darcs-hash:6e46c6a2528c99f3e05bc67837fa9d391d7ecff2

Attempt to guess the location of detachtty and attachtty (Patch by: Jamie Border <jamie@jborder.com>)

darcs-hash:a25da2293e4b833e5087ed0c88064d509d74e5a7

darcs-hash:9a336e7c47e018f4968078305242be6acdeac776

darcs-hash:ab85595b6d71baf4cb4ea58487f8ed409b771e43

darcs-hash:f66925fdefd3482f39778fa0152d8ebcd1239877

darcs-hash:35f884e78a8347e4d29294598fef2a1760ed7af7

Remove lispworks note about ASDF. We must eb able to assume that basic setup of ASDF is done before loading UCW.

darcs-hash:cb1903a5e288abd5ff80ebe5730ba0db98d81b82

darcs-hash:21f0a7777a36c2c1a6dbfba079184c8cdd8daece

darcs-hash:3aa2343aa7540aecf62b4d726bf65db82e30f982

darcs-hash:132668fc521cc6fe7fa1f8c96ef717d1c339a735