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

Re: checkout to stdout (cvs -p)?

From: Saku Ytti <saku+svn_at_ytti.fi>
Date: 2006-05-18 14:10:19 CEST

On (2006-05-18 14:02 +0200), Giovanni Bajo wrote:

> > Yes, thats what I want. However I can happily 'cat' every file with
> > SVN binary itself in a lets say for loop generated from 'ls'.
> > Only difference in perl bindings would be, that I don't have to start
> > svn binary at all. But I would have to call the perl script inside
> > another script, so that I could get the data in perl array. While
> > what I'd like to do, is to directly either a) in perl put the data
> > in array or b) make svn binary output to stdout each file in
> > directory.
> Can't you have one per script which does *only* the equivalent of cvs -p
> through the Perl bindings, and then you run it in pipe with the other one
> which processes the output? Composition of small components through pipes is
> how this kind of scripts is always designed.

Yes I could, now I'm calling CVS binary from perl, once. With
this method I'm calling perl/python script inside perl, once. The
program speed is currently bound by cvs checkout speed, so I guess
even though I'd replace CVS binary calling to perl/python script
it might still be faster.
But to be honest, it's seems more attractive to me to write
the whole shebang in single python program, as it appears
python binding supports catting to an array.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 18 14:11:40 2006

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

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