Greg Troxel [EMAIL PROTECTED] writes:
My own view is that a package configured with --prefix=/usr/foo should
install files only under /usr/foo. This leads me with guile to want
to extend load-path to include guile directories in other prefixes.
On this point I think I disagree with you.
[EMAIL PROTECTED] (Ludovic Courtès) writes:
I like this approach quite well. It's generic, and it can be used
handle both Guile versioning and module versioning. Having it in
`init.scm' or some such rather than hardcoded at configuration time
sounds like a good idea too.
Thanks. I'm about
Greg Troxel [EMAIL PROTECTED] writes:
I concur with most of your comments, but would like to make a
metapoint: various OS/distributions/packaging systems have rules about
what goes where, and guile should be such that it can be made to
behave 'right' for these varying definitions of right. I
Neil Jerram [EMAIL PROTECTED] writes:
Greg Troxel [EMAIL PROTECTED] writes:
Yes, thanks. This is exactly what was in my mind too, but I didn't
make that clear.
Glad I was helpful - was feeling redundant but posted anyway.
Basically, when I'm using a distribution (Debian in my case), I
Kevin Ryde [EMAIL PROTECTED] writes:
Neil Jerram [EMAIL PROTECTED] writes:
Can someone tell me the Makefile.am incantations for determining where
a package should install Scheme and Elisp files?
For the lisp bits, AM_PATH_LISPDIR in configure.ac then
dist_lisp_LISP = foo.el
or if
I concur with most of your comments, but would like to make a
metapoint: various OS/distributions/packaging systems have rules about
what goes where, and guile should be such that it can be made to
behave 'right' for these varying definitions of right. I think this
is implicit in your comments,
