Re: cvs2svn.py and Python bindings on Windows

Florian Schulze <florian.proff.schulze@gmx.net> writes:
> I was today able to compile the Python bindings for Windows with a
> small problem. The generated C files from SWIG have (long long) in
> them when there should be (__int64). I use SWIG 1.3.17. After I fixed
> that manually the bindings compiled without problems. I don't know if
> they work flawless, because I only tried cvs2svn.py yet, see below.

Maybe you're not aware that cvs2svn.py no longer uses the SWIG/Python
bindings? It just depends on the 'svnadmin' binary being available.

If your cvs2svn.py requires the bindings, then it is *very* old and
you should update.

> cvs2svn.py is another problem. I had to add binary to some (4 or so)
> file open calls, so the CVS repository is parsed correctly. The popen
> call has the buffersize set to something like 108..., which doesn't
> work on Windows, which wants -1 or nothing (not specified) for the
> buffersize. After these changes the SVN repository was filled, but
> there was no path seperation done. The files had names like
> "\path\Makefile" which can't be checked out.

Can you post the patch you made? (If you have time to write a log
message for it, that's great, but it's fine to just post the change if
not.)

Also, I'm not sure exactly what you mean by:

   ...but there was no path seperation done. The files had names
   like "\path\Makefile" which can't be checked out.

Could you describe precisely what happened?

Thanks,
-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 27 18:17:04 2003