[clbuild-devel] patch for new packages

[David Lichteblau]

Hi,

(haven't applied your diff yet, just some quick comments:)

Quoting Jianshi Huang (jianshi.huang at gmail.com):
> I've added several packages into clbuild and also changed some code in
> clbuild script. I don't know how to create the patch so I'll just
> paste the "darcs diff" result here.

"darcs diff -u" would have been even better.  (Or perhaps "darcs send".)

> Things I've changed in clbuild:
> 
> * put definition of build_options and run_options after the definition
> of common_options

Thanks for the bug fix.  I must have broken that recently.

> * remove '--disable-debugger' from build_options under the SBCL
> configuration (there's a package lock warning when compiling lisa)

Well, I think the Lisp is meant to exit when building fails.

If one system in a larger project doesn't compile properly, it can be
blacklisted using BLACKLISTED-SYSTEMS in CLBUILD::RECOMPILE-SYSTEMS.

If a project doesn't compile properly at all, it would be better to fix
that problem first, of course.  (But admittedly, I already violated that
rule when adding eclipse and, more recently, cl-jpeg.)

> Packages I've added:
> 
> * s-xml-rpc
> * zebu
> * series
> * lisa
> * parse-html
> * cl-opengl

I think some of these should wait until I have an implementation of that
`wnpp-projects' idea.  But I hope to find time for that soon.

> Problems I've met:
> 
> * don't know how to specify the .asd file to be loaded when building a
> package. (contextl comes with 3 .asd files, only 1 should be loaded)

These days, we use the asdf-install rule:
  - A project is translated to all systems for which a SYSTEM.asd is
    found in the project directory.
  - All systems belonging to the project are LOAD-OPed, unless
    blacklisted as mentioned abov.

If an .asd file is hidden in subdirectories, code needs to be added to
the clbuild script that symlinks it manually.  We don't compile such
systems explicitly though, only if they occur as dependencies of main
systems.


Thanks,
David