[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-users] Packaging practices
From: |
sunnan |
Subject: |
[Chicken-users] Packaging practices |
Date: |
Sun, 6 Nov 2005 17:27:06 +0100 (CET) |
User-agent: |
SquirrelMail/1.4.4 |
Hi,
What are, in this list's opinion, the recommended best practices for
distributing free software written in Chicken? I'm thinking proper
GNU-style source tar balls, since that's currently the basis for most
further (distro specific and other binary) packaging.
* Do you use autoconf, if so, what do you check for?
* What about automake?
* Do you make one distribution containing the full .scm-files and one
with just the .c-files, or do you only make the .scm-distribution?
* How do you deal with third-party eggs from the
call-with-current-continuation repo that your program uses?
I'd love to see example chicken projects, I'm especially interested in
autoconf and automake usage but other solutions are also of interest.
Sunnan
- [Chicken-users] Packaging practices,
sunnan <=