daviid
pushed to devel at cwebber/guile-squee
80ce6ad47e autotool chain - final step
Let's get it working now!
* .gitignore:
* Makefile.am:
* am/guile.mk:
* autogen.sh:
* configure.ac:
* env.in:
* m4/guile.m4:
* meta/guile-squee-1.0.pc.in: New files. With all these, Guile-Squee is
now fully autotool chained!
- c816c6bf30 autotool chain - step 3
Let's add a Guile-Squee documentation mockup.
* doc/Makefile.am:
* doc/fdl.texi:
* doc/introduction.texi:
* doc/preface.texi:
* doc/squee.texi:
* doc/using.texi:
* doc/variables.texi: New files.
- 920ba43545 autotool chain - step 2
Let's move Guile-Squee source code to 'squee/'. The top-level squee.scm
imports squee/*.scm modules, re-exporting their public interface when
appropriate. The top-level squee.scm is the only module the user has to
and should import to play with Guile-Squee.
The original squee.scm has been moved to squee/, the top-level squee.scm
is new, but but git thinks it's been copied and modified, hence the
silly git diff report if you try that...
Dave, Christoffer, I'd like to talk about how we could/should do wrt
Guile-Squee's API, but right now the objective was/is to set-up a good
module organization, then we can work on how to name things and what
should be API...
* squee.scm:
* squee/enum.scm:
* squee/reexport.scm: Added.
* squee/squee.scm: This is actually Christoffer's original version,
except that I did split it in 2, as an example, and moved the enum
functionality to a separate module.
- 5a6c294ab3 autotool chain - step 1
* AUTHORS:
* ChangeLog:
* INSTALL:
* LICENSE:
* NEWS:
* org/squee-BUGS.org: Added.
* squee-TODO.org: Moved to org.
* COPYING.txt: Renamed to COPYING.
* README.txt: Renamed to README.
- View comparison for these 4 commits »
9 years ago
a85902a92b Use ice-9 format