Ryan Schmidt wrote:
> Ok, then do it on the fly. You never mentioned multiple projects before;
> you spoke of "the project" implying there was only one. Having pre-made
> tarballs on the server that the user can just click to download would be
> faster for the user at the time they want to download it. But if there
> are too many projects for this to be practical, then export the code
> from the repository and generate the tarball at the time the user clicks
> download.
FWIW, you may find that SVN::Notify::Snapshot[1] will make this process
trivial to code. That module automatically handles the export and
tarball generation. It was originally intended to be called as part of
a post-commit hook, but there is no reason you couldn't call it from a
web page on any requested path. And if there is a path that is
requested more often, you could pre-generate that tarball in a
post-commit so that it is always "current". See SVN::Notify::Config[2]
for an easy way to fire different post-commit actions based on regex
matches (e.g. create snapshots when someone creates a tag matching
"RELEASE-").
John
1. http://search.cpan.org/dist/SVN-Notify-Snapshot/
2. http://search.cpan.org/dist/SVN-Notify-Config/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 10 14:58:09 2007