Re: 1.6, Guile's shared libraries, Debian packaging, and versioning.

[Gary Houston]

> From: Han-Wen <address@hidden>
> Date: Thu, 25 Jul 2002 22:55:49 +0200
> 
> address@hidden writes:
> > Han-Wen <address@hidden> writes:
> > 
> > >     /usr/lib/guile-1.6/libguile.so.12
> > >     /usr/lib/guile-1.6/libsrfi-4.so
> > >     /usr/lib/guile-1.6/scm/frob.scm
> > > 
> > > etc. guile-config can return the proper -L flags for linking. 
> > > 
> > But how about the run-time linker? This would mean one has to mess
> > with LD_LIBRARY_PATH or /etc/ld.so.conf (on GNU/Linux). Furthermore it
> > makes no sense IMO to have versioned libraries in a subdir (like
> > libguile.so.12 in the example above). Note also that the srfi libs are
> > versioned, at least on my system.
> 
> ok, point taken, but unversioned files should go into a version
> directory, then.

In this scheme, would leaving libguile in /usr/lib for easier linking
cause any problems?

Would it be reasonable to expect C code to always use libguile (module
system) to access modules, instead of linking dynamic libraries
directly?  (Apart from this needing fixes to the module system, since
at present it doesn't retain the dynamic library handle after running
the library's init function.)