> -----Original Message-----
> From: C. Michael Pilato [mailto:cmpil...@collab.net]
> Sent: Wednesday, June 13, 2012 9:34 PM
> To: dev@subversion.apache.org
> Cc: Hyrum K Wright; comm...@subversion.apache.org
> Subject: Re: svn commit: r1349944 - /subversion/trunk/gen-make.py
>
> On 06/13/2012 07:36 PM, Hyrum K Wright wrote:
> > On Wed, Jun 13, 2012 at 6:10 PM, <rhuij...@apache.org> wrote:
> >> Author: rhuijben
> >> Date: Wed Jun 13 16:10:25 2012
> >> New Revision: 1349944
> >>
> >> URL: http://svn.apache.org/viewvc?rev=1349944&view=rev
> >> Log:
> >> * gen-make.py
> >> Make the --with-neon= and --without-neon arguments on gen-make.py
> optional,
> >> just like how ./configure handles those. Windows doesn't use ./configure
> and
> >> this breaks tools that are friendly enough to provide hints.
> >
> > I don't like this change. ./configure *doesn't* work this way: it
> > errors when attempting to provide the now-defunct neon options.
>
> Perhaps Bert meant only that, in general, configure allows you to specify
> options that it doesn't itself understand (while printing a warning about
> this fact).
I think most distributions at least share some build code between versions.
The buildbots only have a single set of dependencies for all the branches we
are building. Only once we released 1.9.0 neon will be gone and before that we
still have to support it (and even after that we still have to support all the
Subversion 1.0-1.7 clients that still use neon)
Things get very easy if you just break the few remaining buildbots without
caring about the consequences, but it doesn’t make Subversion a better product.
Bert
