SF Markus Elfring wrote:
>> Is there a reason you're calling for autoconf 2.61 in
>> bacula/autoconf/configure.in, but autoconf 2.59 in
>> gui/autoconf/configure.in?
>
> Yes, of course.
>
> The value "2.61" was specified previously. I see the value "2.59" as recent
> enough for an update from "2.13" of the requirements check. Do you need newer
> tools?
I don't know that we specifically need a particular version, I just
think we should be consistent about what we require. Different version
requirements in different places in the same source tree is a fast route
to madness.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org
Renaissance Man, Unix ronin, Perl hacker, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
