On 7/3/2010 10:23 PM, Russ Allbery wrote:
>> README-WINDOWS can and should be folded into README.
>
> Agreed.
Personally I would like to see README have a pointer to another
file that is located in the doc tree for the Windows environment
setup. README-WINDOWS is a non-trivial amount of text tha
Jeffrey Hutzelman writes:
> Russ Allbery wrote:
>> I think it's confusing to put things into acinclude.m4 that are only
>> used by configure.in. This is unlike the way nearly every other free
>> software program using Autoconf uses its configure.ac file and is
>> unnecessarily confusing for con
--On Thursday, July 01, 2010 01:43:51 PM -0700 Russ Allbery
wrote:
No thanks. I'd much rather have one "main program" than two, even if
that means conditionalizing some things on which configure script we're
building, as acinclude.m4 currently does. I actually believe the
current split is cl
Jeffrey Hutzelman writes:
> Russ Allbery wrote:
>> One of the things that makes OpenAFS's configure script difficult to
>> maintain right now is the giant acinclude.m4 file, which is the
>> equivalent of putting all the code of a complicated module in a single
>> function. Breaking code into sep
--On Thursday, June 24, 2010 01:20:10 PM -0700 Russ Allbery
wrote:
One of the things that makes OpenAFS's configure script difficult to
maintain right now is the giant acinclude.m4 file, which is the equivalent
of putting all the code of a complicated module in a single
function. Breaking code
Moving this here from Gerrit. This is a proposal, not a finalized
position. Please review and comment, and then we'll take some form of
this and put it into README.DEVEL.
One of the things that makes OpenAFS's configure script difficult to
maintain right now is the giant acinclude.m4 file, which
