On 13/09/2007, Keith M Wesolowski <keith.wesolowski at sun.com> wrote: > On Thu, Sep 13, 2007 at 10:41:58AM -0700, Dermot McCluskey wrote: > > > framework. However, the manpage will clearly state that libtool > > is not recommended for use outside the autotools framework or > > for new projects that are not already committed to its use. > > This case classifies the interfaces as Uncommitted and adds the > > Obsolete modifier to indicate that the tool is not advised for > > general use. > > > > The version proposed here is the latest stable version available. > > > > Libtool is delivered as: > > - Two command-line programs, libtool and libtoolize. > > These scripts will be installed in /usr/bin. > > Given the above, why are we delivering libtoolize? According to > http://sunsite.ualberta.ca/Documentation/Gnu/libtool-1.3.5/html_node/libtool_30.html, > it "provides a standard way to add libtool support to your package". > Since libtool is Obsolete and should not be used by new projects, it > seems that we should not deliver this program.
The page you linked to outlines the reason: "`libtoolize --automake' is used by Automake to add libtool files to your package, when AM_PROG_LIBTOOL appears in your `configure.in'." Developers that are contributing to existing open source projects that use libtool will unfortunately need this. -- Shawn Walker, Software and Systems Analyst binarycrusader at gmail.com - http://binarycrusader.blogspot.com/ "Beware of bugs in the above code; I have only proved it correct, not tried it. " --Donald Knuth
