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 disa
[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 ab
I think this meets everyone's desires ... please let me know what you
think!
Neil
-*- scheme -*-
;; 1. Format and example contents of
;; $sysconfdir/guile/$EFFECTIVE_VERSION/config.scm
;;
;; The format is a single alist expression which Guile reads.
;; (config.scm i
We need remove-load-path too, for cleanup.
It's not clear to me how the default version of config shows up in a
fresh guile build/install. I'd argue that only the traditional three
dirs in prefix should be there by default. Perhaps configure can have
a "--add-load-path /usr/local/share/guile" to
Greg Troxel <[EMAIL PROTECTED]> writes:
> We need remove-load-path too, for cleanup.
OK.
(Actually, "add" should probably be "ensure", and only add the
directory if not already in config; and "remove" should probably be
"cleanup", and only do anything if there is nothing left under the
relevant
Yes it does (I think). If that's what you want, you just write your
Makefile.am like this ...
scmdatadir = $(datadir)/guile
scmdata_DATA = whatever1.scm whatever2.scm
... and add an extra install step (for which I forget the syntax)
that does
guile-config add-load-path mydata
Greg Troxel <[EMAIL PROTECTED]> writes:
> Yes it does (I think). If that's what you want, you just write your
> Makefile.am like this ...
>
> scmdatadir = $(datadir)/guile
> scmdata_DATA = whatever1.scm whatever2.scm
>
> ... and add an extra install step (for which I forget the syntax)
