Hi, I just set up a guile library for the kids manually, naturally configuring with
./configure --prefix=$HOME/.local
to avoid interfering with other user accounts, and setting up the
correct %load-path and %load-compiled-path was much more of a hurdle
than I expected.
I managed it, but it took several minutes, and I hacked it into ~/.guile
in the end, because setting GUILE_LOAD_PATH in ~/.profile did not work
(and even writing that already took time).
For new learners that’s quite a bad first impression.
Is there a good reason why we do not include the site dir and the
site-ccache dir in $HOME/.local in the %load-path and
%load-compiled-path by default (if they exist)?
And if there is a reason, could we re-think whether it is still worth
the cost?
It puts up quite a barrier for adoption (much more than I thought).
It would be really nice if
git clone LIBRARY_URL && cd folder/ && \
autoreconf -i && ./configure --prefix=$HOME/.local && \
make && make install && guile
or
wget LIBRARY_TARBALL_URL && tar xf TARBALL && cd folder / && \
./configure --prefix=$HOME/.local && \
make && make install && guile
would automatically enable importing from the library.
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
https://www.draketo.de
signature.asc
Description: PGP signature
