[elephant-devel] Documentation / Backends
Robert L. Read
read at robertlread.net
Sun Mar 25 18:31:24 UTC 2007
On Sun, 2007-03-25 at 05:17 +0200, Pierre THIERRY wrote:
> FWIW, I think the less built files in the version control the better.
> Apart from bootstrapping purpose, they better be released separately,
> I'd say.
>
> Having them as separate tarballs or single files on the project's
> website is enough, I think.
I completely agree with this. We shouldn't put anything that is
compiled into the the source
control repository.
When we make a release, we will always want to construct a appropriate
tar balls (and, as people
have point out, this may include documentation) in any case as part of
the release process.
I'm pleased that we're making progress towards a more robust build
process, and it certainly
seems we are becoming more completely multi-platfrom. Ian is doing most
of the actual work,
but obviously, if a multi-LISP, multi-OS, multi-backend system it takes
patient and informed
testers such as y'all to make this process work.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/elephant-devel/attachments/20070325/2bb56734/attachment.html>
More information about the elephant-devel
mailing list