[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: John Szakmeister <john_at_szakmeister.net>
Date: 2005-10-15 16:22:44 CEST

On Friday 14 October 2005 09:40, Michael Sinz wrote:
> 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....

There's already something like that there there, though I've never used it:
 $./configure --help
                         do not check the Neon version

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 15 16:23:27 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.