From: Andreas Rottmann <a.rottmann@gmx.at>
Subject: Archive of Guile standard library available
Date: Wed, 24 Mar 2004 15:38:36 +0100 [thread overview]
Message-ID: <87d6725mz7.fsf@ivanova.rotty.yi.org> (raw)
Hi!
I've now checked-in the Guile library (0.1) tarball into my guile-2004
archive[0]. I've done some slight modifications on the source (mostly
re-indenting; could we agree not to exceed 80 chars/line, when
possible?). I also switched the buildsystem to Tom Lord's
package-framework, mainly because it
1) lowers maintainance costs (less Makefile changes)
2) allows for easily shipping guile-lib with your project (assuming
that project uses package-framework as well): You just build a
config[1] like this:
./src lord@emf.net--2004/package-framework--devo--1.0
./src/itla a.rottmann@gmx.at--2004-main/itla--devo--0.1
./src/guile-lib rotty@debian.org--guile-2004/guile-lib--head--0.1
Then, your users just have to build-config that, and are equipped
with the version of guile-lib you specified; which might be a
not-yet-released one.
I hope I don't get flamed for not using automake ;), but I think it's
very important for the sucess of guile-lib that developers can easily
ship it with and integrate it into their projects.
[0] http://people.debian.org/~rotty/arch/rotty@debian.org/guile-2004/
[1] http://regexps.srparish.net/tutorial-tla/multi-tree-projects.html
Andi
--
Andreas Rottmann | Rotty@ICQ | 118634484@ICQ | a.rottmann@gmx.at
http://yi.org/rotty | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62
Make free software, not war!
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2004-03-24 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-24 14:38 Andreas Rottmann [this message]
[not found] ` <871xnib15i.fsf@buug.org>
2004-03-24 20:14 ` Archive of Guile standard library available Andreas Rottmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d6725mz7.fsf@ivanova.rotty.yi.org \
--to=a.rottmann@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).