From: Thien-Thi Nguyen <ttn@glug.org>
Cc: guile-user@gnu.org
Subject: Re: cmod-play 1 available + modsup.h additions
Date: Fri, 14 Nov 2003 12:38:01 -0500 [thread overview]
Message-ID: <E1AKhtR-0004Zj-00@colo.agora-net.com> (raw)
In-Reply-To: <20031114133735.GC16650@powergnu.laas.fr> (message from Ludovic Courtès on Fri, 14 Nov 2003 14:37:38 +0100)
From: Ludovic =?iso-8859-1?Q?Court=E8s?= <ludovic.courtes@laas.fr>
Date: Fri, 14 Nov 2003 14:37:38 +0100
I actually don't see the point in having different namespaces for
Guile things. :)
what you don't see i can't make you see, but i'm happy to understand
your not seeing and leave it at that. i'll probably change "M" to
"GH_M", that is, add to GH_ rather than appropriate another namespace
entirely. thanks for the feedback.
The doc snarfing example you gave is a nice thing. Unfortunately,
there is no such thing in Guile 1.6. Is there any reason for
continuing development for 1.4.x rather than working on 1.6.x?
there are practical reasons having to do w/ lack of write access to the
repository, primarily. a secondary reason is that 1.6.x introduces
onerous "deprecation" machinery, and insists on installing lots of
un-neighborly shared object libraries in ${libdir}, which would be
difficult to reconcile w/ 1.4.x's compatibility and encapsulation goals.
1.7.x has lots of internal improvements (that i will snarf for 1.4.x
once they settle down) but its packaging still suffers the same problems
as 1.6.x as far as i can tell (from watching the cvs commits m.l.).
re doc snarfing, you might try to simply overlay the 1.4.x scripts/
subdir over that of the other branches, or add its parent dir to
GUILE_LOAD_PATH, or explore guile-tools options `--scriptsdir' and
`--guileversion' (see "guile-tools --help").
i've been toying w/ the idea of excerpting and releasing scripts/ as a
separate package entirely, for the benefit of other guile branches, but
haven't found the time/inclination. feel free to complete this program
and put your name on it, etc.:
#!/bin/sh
# $1 is an optional tag spec, like "-D DATE" or "-r TAG"
set -ex
cvs -d :pserver:anonymous@cvs.glug.org:/home/ttn/cvsroot \
co -d guile-scripts $1 guile-core/scripts
cd guile-scripts
cp -p ${someplace}/{autogen.sh,configure.ac,Makefile.am,...} .
sh -x autogen.sh
./configure -C --enable-maintainer-mode --prefix /tmp/a/b/c
make
make check
make install
make installcheck
make uninstall
make dist
mv guile-scripts-*.tar.gz ..
cd ..
rm -rf guile-scripts
you just need to define ${someplace} and put the correct files there.
if you publish this package you would help other users invest in their
freedom (should they have the desire to do so).
thi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2003-11-14 17:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 21:55 cmod-play 1 available + modsup.h additions Thien-Thi Nguyen
2003-11-14 8:26 ` Ludovic Courtès
2003-11-14 13:10 ` Thien-Thi Nguyen
2003-11-14 13:37 ` Ludovic Courtès
2003-11-14 17:38 ` Thien-Thi Nguyen [this message]
2003-11-14 14:29 ` Marius Vollmer
2003-11-14 14:17 ` Marius Vollmer
2003-11-14 15:28 ` Does anyone have a better scm_string_hash ? Roland Orre
2003-11-14 15:51 ` Ludovic Courtès
2003-11-17 8:33 ` Roland Orre
2003-11-17 13:01 ` Ludovic Courtès
2003-11-17 15:42 ` Marius Vollmer
2003-11-17 16:02 ` Marius Vollmer
2003-11-17 16:29 ` Marius Vollmer
2003-11-17 16:48 ` Allister MacLeod
2003-11-17 17:57 ` Marius Vollmer
2003-11-17 19:17 ` OT: x86 assembly timings/size (was Re: Does anyone have a better scm_string_hash ?) Allister MacLeod
2003-11-17 21:27 ` OT: x86 assembly timings/size Marius Vollmer
2003-11-19 9:04 ` Does anyone have a better scm_string_hash ? Ludovic Courtès
2003-11-19 15:02 ` Marius Vollmer
2003-11-14 17:40 ` cmod-play 1 available + modsup.h additions 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=E1AKhtR-0004Zj-00@colo.agora-net.com \
--to=ttn@glug.org \
--cc=guile-user@gnu.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).