From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: "John Trammell" <johntrammell@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: packaging a guile module, call/cc tutorial
Date: Sat, 31 May 2008 09:14:34 +0200 [thread overview]
Message-ID: <87iqwvaqsl.fsf@ambire.localdomain> (raw)
In-Reply-To: <68dbb6fe0805301228m610dab58o2547427b967abf01@mail.gmail.com> (John Trammell's message of "Fri, 30 May 2008 14:28:45 -0500")
⎛⎞ "John Trammell" <johntrammell@gmail.com>
⎝⎠ Fri, 30 May 2008 14:28:45 -0500
I'd like to tar up and make available as a GPL'ed installable
package. Can any of you point me to documentation or an
example of how to do that? I have something cobbled together
with a Makefile but I'd like to think there's a more
sophisticated solution out there.
Not terribly sophisticated, but i can recommend Guile-WWW[0].
Pros:
- includes documentation (=> doc extraction/munging)
- includes testing (=> "make check" => pre-install usage)
- uses "standard" autotools methodology
- supports Guile 1.4.x and later
Cons:
- no C bits
For C bits, i don't know of any definitive cross-version methodology
yet. The one i use, which requires 1.4.x support, is boiled down
into the cmod-play package[1]. All the other gnuvola.org/software
that have C bits (e.g., Guile-PG) are based on it. On my todo
list is to find a path towards such a unified methodology; if/when
that happens, cmod-play will be updated to reflect my findings.
thi
___________________________________________________
[0] http://www.gnuvola.org/software/guile-www/
[1] http://www.gnuvola.org/software/cmod-play/
next prev parent reply other threads:[~2008-05-31 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 19:28 packaging a guile module, call/cc tutorial John Trammell
2008-05-31 7:14 ` Thien-Thi Nguyen [this message]
2008-05-31 15:16 ` Neil Jerram
2008-06-03 15:18 ` Ludovic Courtès
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=87iqwvaqsl.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-user@gnu.org \
--cc=johntrammell@gmail.com \
/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).