Hello John!
On Dienstag, 3. Juli 2007, John Peacock wrote:
...
> However, every single method of generating an export/dump/whatever from
> scratch every time will take much CPU on the server.
I don't know how much that matters, if I'm going to do a compressed tar
anyway.
Doing a bzip2 (or even only gzip) takes more time than getting the data out of
the repository, no?
> If you can have a
> single working copy on the server that is always in sync with the trunk
> (or whatever branch you are distributing), then you could either tar or
> otherwise stream that to as many computers as you want daily.
Yes, it *may* be worthwile that some directory is updated, and a tar is taken
from there.
> If, on
> the other hand, the image changes radically from day to day, there is no
> other current solution I am aware of that would work.
Hmmm, the change rate? Good question. Normally small, but if eg. openoffice is
replaced, thats 100MB in a single change...
> That being said, I could see using the bindings to read the repository
> directly and output something like a tar stream, but that would require
> two expertise:
>
> 1) using the bindings
> 2) knowing the tar file format to generate on the fly
>
> Essentially, it would be a matter of writing a recursive cat that
> embedded the files into a tar stream on the fly...
Later in this thread a svntar is mentioned; it seems to work.
Thank you for your thoughts!
Regards,
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 4 07:53:05 2007