Re: suggestion

[I've removed cmucl-help and added cclan-list to the CC line: hope
this is OK]

John Klein <[email protected]> writes:

> Thanks for the lead. CCLAN seems to be a superset of what I
> wanted. I had glanced at it before, but it was a bit more inchoate
> then.  Is there an 'idiot's guide to using vn-cclan' [the

It's gratifying to know that we're perceived as less inchoate than at
some previous date: that could almost be seen as progress ;-)

All the docs on cclan so far have been produced by people who are
probably too close to it to get a real handle on what new users are
looking for, so if you're not "getting it" from the links I posted in
the previous message, I think the answer to that one must presently be
"no".

* as a user

0) (once-only operation): grab and install a copy of asdf.  For ease
   of use, dump a lisp image that includes it, or add it to your lisp
   init files.  

1) (likewise, once-only) decide where you want to keep the symlink
   farm for all your cclan packages.  We use $HOME/lisp-systems/ in
   our examples, but this could be a system-wide directory if you have
   the appropriate privileges.

2) observe that you wish to install a package which lives in vn-cclan.
   Download it either by cliking on the "download from" link on its
   cliki page, or directly from your nearest vn-cclan mirror
   (http://ww.telent.net/cclan/ has a list)

3) untar it, follow the instructions in the README.cCLan-install file
   that should be there.

* as a package developer

0) grab the cclan.lisp file that you'll find alongside asdf.lisp in CVS

1) write a asdf-compatible system definition for your package that
   includes all the files you want to be distributed in the tarball.
   See http://ww.telent.net/cliki/asdf_system for the rules and
   existing vn-cclan packages for examples

2) load cclan.lisp (compile it first, if you like) and run
   (cclan::make-tar-file 'my-system-name)

3) post to cclan-list to find an archive node maintainer who can
   upload it.  Send them the tar file in some mutually agreed-upon
   fashion

* interaction with vendor packaging systems

depends very much on the vendor and where they want to put things in
the filesystem.  The appropriate sections of 
http://ww.telent.net/cliki/ASDF%20System may or may not make sense:
I'm not sure that they do, feedback is welcome on that page or by mail

> vendor neutral 2nd generation] available, or is this on the to-do
> list?  Is there a documentation format yet?

There is no agreed documentation format, though there are a couple of
candidates.  Personally I like mine ...

  http://ww.telent.net/api-reference.html

  is the documentation for db-sockets, assembled from #|| ||# comments
  in source code, arglists, and doc strings.

Christophe will be along in a minute to talk about his competing doc
format, I expect


-dan

-- 

  http://ww.telent.net/cliki/ - Link farm for free CL-on-Unix resources 


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390