On May 25, 2009, at 6:16 PM, Marco Maggi wrote:
"Abdulaziz Ghuloum" wrote:
Fasl files (i.e., precompiled, binary library files)
currently go into the same place where the library is.
[...]
Should this change? And what to?
OS-specific policy?
We have one OS so far, so, one policy.
For Unix-like systems I would like two specifications:
1. Where to search for precompiled FASL files.
2. Where to put new FASL files.
For "where to search" I like a user configurable search path, as
it is
now with "IKARUS_LIBRARY_PATH".
Why would you want multiple cache directories?
I want the following possible SLS
installation directories:
$prefix/share/scheme
$prefix/lib/scheme
$HOME/share/scheme
$HOME/lib/scheme
Ikarus doesn't put anything in $prefix/share/scheme or $prefix/lib/
scheme
and there is no standard/srfi/os policy stating where scheme library
files
should go in the OS. If you want this (and it is a good thing), you
need
to get some agreement from implementors and/or OS package maintainers as
there may be issues or conventions that I don't want to violate.
and the FASL directories listed below.
For "where to put" I would like:
- Default as it is now; it allows both compile-then-
install and
install-then-compile.
You should be able to get the current behavior by setting the fasl path
to be "/".
- Optionally, put FASL under one of the following:
$prefix/lib/ikarus/<spec-pathname>
/var/ikarus/$USER/<spec-pathname>
$HOME/var/ikarus/<spec-pathname>
$HOME/.ikarus/<spec-pathname>
What's <spec-pathname>?
It can be done with an environment variable and a command line
option
(option supersedes variable) selecting a directory.
Yes. Ideally.
OT: I would also like FASL self-completeness and independence
from the
source file; with dependence between the FASL and the SLS compile
time
selection of FASL directories, administration problems may arise.
As I said before, this is not a priority.
Aziz,,,
