On Sat, Aug 30, 2008 at 1:07 AM, Luca Capello <[EMAIL PROTECTED]> wrote: > This bug has nothing to do with the rpath issue (now solved [1]). > Thus, the problem remains: is there any particular reason for > /usr/lib/libecl.so not providing a SONAME?
That is not something ECL has to provide. It is more a configuration option that operating systems may provide. The question is whether it is worth. You have to consider the following: with every binary release we are adding more functions and the names of old ones change. That means being a rapidly evolving project we are definitely going to break binary compatibility very frequently. I should rather say with every release. Furthermore, ECL is currently not being used as a library by any project. It is only either a runtime for compiled files or the interpreted environment itself. Do you expect SBCL to use some kind of SONAME for its core? Not really. Juanjo -- Instituto de Física Fundamental CSIC, Serrano, 113, Madrid 28040 (Spain) http://juanjose.garciaripoll.googlepages.com _______________________________________________ pkg-common-lisp-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-common-lisp-devel
