The (compile... and (install... forms are actual shell commands, while the rest is metadata. I am not saying they must be in separate files, but they are semantically different, so you can't just mash them together like that.
-Ivan "Shawn Rutledge" <[EMAIL PROTECTED]> writes: > On Mon, Apr 14, 2008 at 4:05 AM, felix winkelmann <[EMAIL PROTECTED]> wrote: >> If you allow me to say so: chicken-setup needs a rewrite. > > In that case I have a couple more ideas: > > Take the version number from the svn tag so I don't have to keep > changing the setup file every time. > > Maybe the rest of the setup information can come from the meta file: > > ((egg "dbus.egg") > (compile -s -O2 -d1 > -ldbus-1 -I/usr/include/dbus-1.0/ -I/usr/lib/dbus-1.0/include > dbus.scm) > (install > (implementation "dbus.so" "dbus.o") > (exports "dbus.exports") > (documentation "extra-doc.html" "yet-more-doc.html" from-wiki) > (examples (list-files "examples/*")) ) > (license "MIT") > (category os) > (author "Shawn Rutledge") > (synopsis "A binding for libdbus, the IPC mechanism")) > > Documentation from-wiki would imply installing the docs from the wiki > in addition to the others in the list (in the right place), and > (exports ...) would imply adding the compile flags to generate the > exports. _______________________________________________ Chicken-hackers mailing list Chicken-hackers@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-hackers