[scponly] subversion support

Dimitri Papadopoulos-Orfanos papadopo at shfj.cea.fr
Thu Apr 7 08:10:31 EDT 2005


OK, I have identified the problem.

For some reason config.h did not define SVN_COMPAT although it had been 
generated using the --enable-svn-compat option flag:
	/* config.h.  Generated by configure.  */
	#define PACKAGE_NAME ""
	#define PACKAGE_VERSION ""
	#define PACKAGE_BUGREPORT ""
	
	/* Features */
	/* #undef UNIX_COMPAT */
	/* #undef IRIX_COMPAT */
	#define WINSCP_COMPAT 1
	#define GFTP_COMPAT 1
	/* #undef RSYNC_COMPAT */
	/* #undef UNISON_COMPAT */
	#define ENABLE_SCP2 1
	#define ENABLE_SFTP 1
	#define ENABLE_WILDCARDS 1
	#define RESTRICTIVE_FILENAMES 1
	/* #undef CHROOTED_NAME */
	#define HAVE_WORDEXP 1
	#define HAVE_GLOB 1


Of course these are rather minor details, but I'm still surprized.
Had anyone used scponly with Subversion before?

In short, here are the changes I had to apply:
* Get files from CVS to avoid minor annoyances with #ifdef's.
* Change 'svn' to 'svnserve' in configure.in or configure.
* Define SVN_COMPAT in config.h after runnign configure.

Dimitri Papadopoulos



More information about the scponly mailing list