[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Libtool 2.4.3 release

From: Gary V. Vaughan
Subject: Re: Libtool 2.4.3 release
Date: Fri, 21 Mar 2014 21:00:23 +1300

Hi Richard,

Thanks for bringing these to my attention.

A very brief look at the names of your patches makes me curious to know more... I've added taking a proper look at them to my TODO, but I don't want to hold up the release for them.

If you have time, I'm keeping a mirror of the Libtool repo in my github account to make submitting pull-requests as easy as possible. If you can find the time to polish the ones you want in the release and submit them via github within a month or so, there's still time to make the release :-)



Gary V. Vaughan (gary AT gnu DOT org)

On Mar 21, 2014, at 5:46 AM, Richard Purdie <address@hidden> wrote:

On Thu, 2014-03-20 at 18:07 +1300, Gary V. Vaughan wrote:
On Mar 20, 2014, at 5:37 AM, Arnout Vandecappelle
<address@hidden> wrote:
[Please keep me in CC, I'm not on the list]
Dear libtool maintainers,

Is there a possibility for a new libtool release in the foreseeable

Yes, absolutely. In fact there are only 2 things ahead of it on my
TODO list:

 1. Figure out why a4ffcdb5e is a regression for test 57
 2. fix test 120 race condition

Unfortunately, Libtool is a complex beast, and we are woefully
undermanned here.
While everything rests on my shoulders, it will be at least another
month before I can start work (I'm in the process of emigrating and
all that entails).

Patches for those 2 items, or any other as yet unknown issues with git
master (or if a
bootstrapped tarball is easier to work with) are extremely welcome,
and could lead to an immediate release...

FWIW I'm another build system maintainer who sees email here. We
currently have 12 patches against libtool:

Some of these are inappropriate for upstream, one or two may have been
merged into libtool, some others may highlight issues, particularly
around the sysroot support.

Unfortunately whilst I have the best intentions (and am still on the
list), I haven't found the time to look into the issues as yet and
figure out if we could get some into a form that they'd be accepted



reply via email to

[Prev in Thread] Current Thread [Next in Thread]