On Sunday 27 December 2009 20:16:41 Phil Stracchino wrote: > 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.
Yes, we should be consistent. That is our fault. We are currently using 2.61 in the main source code directory, because that is the version I have on my development machine, and I am the one that does about 99% of the configure.in changes :-) I do update it from time to time, but not on any regular basis. We'll try to make it a bit more consistent while making these changes ... Kern ------------------------------------------------------------------------------ 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
