Having worked on various different packaging and library installation systems, I've found it's always been a pain when there is either
(a) a loading process that takes time proportional to the number of installed libraries (which either costs linear program startup time or quadratic library installation time like TeX, and can make the mere installation of a library cause a program that doesn't even use it to behave differently), or (b) a central cache file to reduce that cost, which has to be maintained by a special-purpose program to install and deinstall things (which doesn't have a natural merge operation that programs like tar or system package installer tools already know about). If we want libraries whose names are not tied to the file system, can we at least use the file system itself as a cache and install them at a predictable location for the loader? E.g., when installing an sld file that has a library named (frob/nozzle möller), can we just make a file $libdir/mit-scheme-aarch64/sld/frob%2fnozzle/m%c3%b6ller with a pointer (maybe a symlink) to the real library file?
_______________________________________________ MIT-Scheme-devel mailing list MIT-Scheme-devel@gnu.org https://lists.gnu.org/mailman/listinfo/mit-scheme-devel
