From: "Neil Jerram" <neiljerram@googlemail.com>
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 16:16:25 +0100 [thread overview]
Message-ID: <49dd78620805310816l5b0c1c70xa0c00c1b8ae5c321@mail.gmail.com> (raw)
In-Reply-To: <68dbb6fe0805301228m610dab58o2547427b967abf01@mail.gmail.com>
2008/5/30 John Trammell <johntrammell@gmail.com>:
> Hi Guile users:
>
> I have a guile issue and a scheme issue I'm hoping you can help me
> with. My guile issue is that I've built a rudimentary module
> (following the code in
> http://www.gnu.org/software/guile/manual/html_node/Creating-Guile-Modules.html)
> that 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.
This is something I'm conscious of, but currently we have no nice
solution AFAIK.
My idea of what would be a nice solution is that
- it would be trivial for the package author to produce a tarball (or
whatever) for others to download
- when a user downloaded and installed that package, the installation
would automatically take place according to the user's distribution's
packaging system.
> My scheme problem is this: I've been beating my head against the
> call/cc examples I've been able to dredge up, but not feeling like
> I've fully mastered the concept. Can anyone interested please chime
> in on either their favorite resource on call/cc, or an example they
> found useful when learning the concept?
Perhaps you're overestimating the concept, and have in fact understood
it? What do you think you don't understand?
Regards,
Neil
next prev parent reply other threads:[~2008-05-31 15:16 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
2008-05-31 15:16 ` Neil Jerram [this message]
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=49dd78620805310816l5b0c1c70xa0c00c1b8ae5c321@mail.gmail.com \
--to=neiljerram@googlemail.com \
--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).