On Sun, May 25, 2008, Michael Jennings wrote:

> On Saturday, 24 May 2008, at 16:46:32 (+0200),
> Ralf S. Engelschall wrote:
>
> > Can you be more specific, Jeff? The only needs I can imagine is that
> > an RPM 5 _developer_ like you wants to build HEAD on an ancient
> > system.
>
> Surely you can't possibly think that a system not running libtool
> 2.2.4 (released less than 30 days ago) is "ancient?"  rpmfind.net
> knows not one single Linux distribution carrying ANY version of
> libtool 2.x yet.

Sorry, bad expressed by me: I meant not that the system itself is
ancient -- I wanted to say that the shipped Libtool is ancient.

> > But regular users in legacy situations should use the official RPM 5
> > tarballs and for those one doesn't need a locally installed Libtool.
>
> How about RPM team members?  I'm *forced* to use rpm5.org tarballs
> because of our bleeding edge build software requirements.
> [...]

Well, rpm5.org _TARBALLS_ are never a problem as they _CONTAIN_ Libtool
2.2.4. The problem exists only if one is 1. building directly from CVS,
2. without using "devtool standalone" and 3. on a platform with an old
Libtool 1.5.x provided by the system vendor. In all other situations one
AFAIK doesn't have a problem.

                                       Ralf S. Engelschall
                                       rse@engelschall.com
                                       www.engelschall.com