From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: ludo@chbouib.org (Ludovic Courtès)
Cc: bug-guile@gnu.org
Subject: Re: guile-www 1.1.1 & 2.16 problems under guile 1.8.
Date: Fri, 11 May 2007 17:25:25 +0200 [thread overview]
Message-ID: <87fy63o00q.fsf@ambire.localdomain> (raw)
In-Reply-To: <87646zfmki.fsf@chbouib.org> ("Ludovic Courtès"'s message of "Fri\, 11 May 2007 16\:43\:09 +0200")
() ludo@chbouib.org (Ludovic Courtès)
() Fri, 11 May 2007 16:43:09 +0200
Nice that it can detect such things and adapt!
that's the theory, anyway.
However, the `s/make-shared-substring/substring/' occurs only at
module-installation time, which precludes one from running the examples
from within the source directory.
good point. i hadn't thought of that.
Also, while `id.cgi' DTRT (except for `make-shared-substring') so
that it can be run from within the source directory, `you-are-here'
just makes plain `use-modules' that are bound to fail when invoked
from within the source directory.
true.
Maybe all the modules could be moved to a `www' subdir, and then
examples could be generated from `.in' files at configure-time that
start with something like:
${GUILE-guile} -L @top_srcdir@ ...
This way, `(use-modules (www ...))' would work fine.
What do you think?
i think the approach (or something like it) is sound. certainly making
the modules and examples usable pre-install is a worthy goal. thanks
for the suggestion.
thi
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2007-05-11 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 1:13 guile-www 1.1.1 & 2.16 problems under guile 1.8 r. clayton
2007-05-11 7:16 ` Ludovic Courtès
2007-05-11 12:28 ` Thien-Thi Nguyen
2007-05-11 14:43 ` Ludovic Courtès
2007-05-11 15:25 ` Thien-Thi Nguyen [this message]
2007-05-11 23:25 ` r. clayton
2007-05-12 14:06 ` Thien-Thi Nguyen
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=87fy63o00q.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=bug-guile@gnu.org \
--cc=ludo@chbouib.org \
/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).