You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2002/04/08 09:39:39 UTC

DO NOT REPLY [Bug 7823] - Libtool 1.3.4 in tarball

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7823>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7823

Libtool 1.3.4 in tarball

jerenkrantz@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From jerenkrantz@apache.org  2002-04-08 07:39 -------
When I RMed 2.0.32, I rolled with libtool 1.4.2.  So, I agree with you - 
libtool-1.3.5 sucks.  However, other RMs believe that we must use icarus 
to roll.  It uses the FreeBSD ports and I believe that FreeBSD is refusing to 
upgrade to libtool-1.4+ in the ports.  (Much like they are refusing to 
upgrade autoconf.)

I believe this needs to be taken up with the FreeBSD people (specifically 
portmgr@FreeBSD.org).  If/when they decide to upgrade the port on 
FreeBSD, we can get Brian B to upgrade accordingly on icarus.

This is a WONTFIX because FreeBSD needs to make an upgrade.
The only thing we can do is set a policy, but I think that'll be ignored.