svn and autoconf

2011-11-19 Thread tsteven4
In the beta test spirit I tried something I don't usually do, to build gpsbabel under cygwin. 17 7:50svn co http://gpsbabel.googlecode.com/svn/trunk/gpsbabel gpsbabel-svn 18 7:52cd gpsbabel-svn/ 19 7:52./configure 20 7:54make The build fails because autoco

Re: svn and autoconf

2011-11-19 Thread Andreas Krey
On Sat, 19 Nov 2011 08:32:47 +, tsteven4 wrote: ... > >configure: configure.in > >autoconf > > Make has a hard time deciding if it needs to build configure. It ends > up depending on the order the files were pulled during the "svn co" > command. My experience on other projects is that

Re: svn and autoconf

2011-11-19 Thread Daniel Shahaf
Andreas Krey wrote on Sat, Nov 19, 2011 at 17:27:16 +0100: > When producing a release .tar file that shall not use autoconf, > run autoconf, remove the autoconf rule from the makefile, and > tar the result (with or without configure.in). Example: tools/dist/release.py in Subversion's trunk.

Re: svn and autoconf

2011-11-19 Thread Johan Corveleyn
On Sat, Nov 19, 2011 at 4:32 PM, tsteven4 wrote: [...] > Furthermore, this > is an option set in the svn config file, not on the command line, so it > isn't convenient to use it for one command and not another. I think that '--config-option config:miscellany:use-commit-times=yes' ought to do it

Re: Huge diff for one-line change in ASF repository

2011-11-19 Thread Johan Corveleyn
On Sat, Oct 15, 2011 at 2:18 AM, Ryan Schmidt wrote: > On Oct 14, 2011, at 18:52, Johan Corveleyn wrote: >> Ah, but git-svn doesn't seem to honor the invariant that files with >> native eol-style *must* be converted to LF by the client. By not doing >> this, they break things for every other svn c