Re: More on possible problem with Neon 0.25.0 [was Re: 1.3.0 RC1 ready to be rolled]

John Peacock wrote:
> David Anderson wrote:
>
>> Perhaps blocking Neon 0.25.0 outright is a little drastic. Is it
>> possible to simply add a LARGE warning in the configure script if
>> 0.25.0 is found, mentionning the bug and recommending an upgrade?
>
>
> I'd rather have a "--no-neon-version-check" so that someone has to do
> something proactive, rather than just relying on warnings. Unless you
> make the configure script interactive (not going to be met with a lot of
> support), it would best to error out if 0.25.0 was found, but give
> people a way around it should they so choose.

That is a better way to go....

On another note - are you still going to be not including neon in the
source bundle? This issue just had be check the various servers that are
running Subversion today and all of the production machines do *not* have
neon installed outside of what came with the Subversion build.

I know that this will end up being "my problem" but I would guess that I
am not alone in this condition.

-- 
Michael Sinz                     Technology and Engineering Director/Consultant
"Starting Startups"                                mailto:michael.sinz@sinz.org
My place on the web                            http://www.sinz.org/Michael.Sinz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org