Re: Package uninstall uninstalls libltdl

[Bob Friesenhahn]

On Tue, 7 Dec 2004, Albert Chin wrote:
> > The difference is that these other packages don't incorporate packages
> > within themselves.  With libtool 2.0, the package can choose to
> > install its own libltdl and the configure script may make the decision
> > automatically.  If it does so (and particularly if it replaces an
> > existing libltdl), removing libltdl can cause system breakage.
> >
> > Doing a 'make uninstall' for the package can unexpectedly (as far as
> > the user is concerned) break the system.
>
> Then shouldn't the package either use the system libltdl or rename its
> local copy?

Yes, of course.  The current behavior is not strictly a bug but I 
thought that I should bring it up so we can discuss it a bit. 
Libtool 2.0 provides the automated mechanics to decide if there is a 
usable libltdl installed, and what it should do if there is not a 
usable libltdl, or if the user says to install the bundled libltdl 
anyway.  I don't think that libtool provides a means to rename the 
installed libltdl.

Libtool will surely be blamed (even though it does the right thing) if 
users start destroying their systems by unexpectedly uninstalling the 
system's libltdl just because they did a 'make uninstall' on their own 
package.  There are consequences the user needs to be aware of.

Bob
======================================
Bob Friesenhahn
address@hidden
http://www.simplesystems.org/users/bfriesen