Re: install directories

[Rob Browning]

Dirk Herrmann <address@hidden> writes:

> > OK, I'll add (export-all) to Guile and deprecate the old stuff (that
> > is, it will print warnings and a pointer to a longer description of
> > what to do instead).
> 
> I like your proposal a lot.  However, I am not sure about export-all.  I
> had thought this was just meant as an example when you explained your
> proposal.  Is it a good idea to have such a form?  IMO, it is cleaner to
> state explicitly what gets exported.

I'm also a little concerned about export-all.  At least personally, I
wouldn't want to use it.  I'd prefer to expliticly state (export foo)
for everyting that should be visible outside the module.

> I am not sure whether this is portable among systems, but I think it
> should also be possible to store guile stuff in some subdirectory of
> /usr/lib, say /usr/lib/guile.  You load it with:
> 
>   (dynamic-link "guile/<some-lib>.so")
> 
> With your proposal, we don't need to make this a policy, since the
> corresponding scheme level loader can use any file name and location
> anyway.  Making it a policy (assuming that is is portable), however, 
> can be convenient, for example if we add a line -L/usr/lib/guile to the
> output of 'guile-config link'.

I'd thought about this, and I like it from an organizational
perspective, but I didn't know if it might cause other problems.  For
example, as I alluded to in my previous mail, I'm worried that you
might be able to get into nasty shadowing situations.  i.e. what if we
just moved libguilereadline.so to /usr/lib/guile, but the user still
had a /usr/lib/libguilereadline.so.  I'm wondering if there could be
library search order issues.

-- 
Rob Browning <address@hidden> PGP=E80E0D04F521A094 532B97F5D64E3930