Subject: Re: CVS commit: pkgsrc/devel/libtool
To: Jeremy C. Reed <email@example.com>
From: Nick Hudson <firstname.lastname@example.org>
Date: 12/13/2003 10:23:54
On Friday 12 December 2003 7:04 pm, Jeremy C. Reed wrote:
> On Fri, 12 Dec 2003, Jeremy C. Reed wrote:
> > $ pkg_info -L libtool-base | fgrep / | xargs grep bsdi4
> > /usr/pkg/share/aclocal/libtool.m4:bsdi4*)
> > /usr/pkg/share/libtool/libltdl/acinclude.m4:bsdi4*)
> > /usr/pkg/share/libtool/libltdl/aclocal.m4:bsdi4*)
> > Those above should be "bsdi*". (The patches fixed other things too.)
> > I will look at this further. But can anyone share any suggestions or
> > advice on fixing those?
> Thinking about this more. It seems like a waste of time to continue to
> patch old libtool.
Threre's not much point patching the .m4 files - all pkgs in pkgsrc should use
> I also have patches for BSD/OS support for libtool-1.4.2 which have
> various differences to libtool-1.4. And I can provide the fixes for
> libtool-1.5 instead.
If you have diffs against branch-1-5 please send them over.
> Will the new libtool version 1.5 in pkgsrc use the original distfile or
> will it be a custom NetBSD tarball (like now)?
I'll probably generate a tarball against a cvs co of branch-1-5 with your
patches unless we can get a 1.5.1 release tarball.
> If it will use original distfile, should we consider importing libtool
> version 1.5 to pkgsrc-wip?
I have no idea how to use pkgsrc-wip and no real energy to learn
> Is there any expected date with libtool 1.5 will be ready for pkgsrc?
When its ready.