You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Joaquín Ayuso <ja...@obralia.com> on 2004/07/15 10:13:18 UTC

Some problems exporting files

Hello,

      Ok, this is my shchema:

      We are 4 developers working on a site. We have the dev machine
      where we have a dev version of the Site (2.34 GB of java) and we
      wanted to install a version control. The machine works with
      Apache 1.3 customized and Jserve customized also.

      I installed Subversion in another machine since upgrading all
      those Java to Apache 2 could be a headache. My Idea was to import the whole site
      into de repository or various reps and later export the files to
      a mounted NFS directory directly to the first machine. I do this
      programming a post-commit hook with a "svn export" inside.

      Here comes the problem. When I do a commit, the "svn export"
      exports the files, but ALL the files of the repository. This is
      painful since each repository has 180 MB of data inside...

      Is there any way to solve this? Is there any way to make an
      export of just the committed files? the --revision COMMITTED
      does actually not work in that way...

      Any solution for this??

-- 
Best regards,
 Joaquín                          mailto:jayuso@obralia.com


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Some problems exporting files

Posted by François Beausoleil <fb...@ftml.net>.

Joaquín Ayuso wrote:

>       Here comes the problem. When I do a commit, the "svn export"
>       exports the files, but ALL the files of the repository. This is
>       painful since each repository has 180 MB of data inside...

That's the description of the export command...

>       Is there any way to solve this? Is there any way to make an
>       export of just the committed files? the --revision COMMITTED
>       does actually not work in that way...

What you would need is a working copy, and you would then update it.  At 
worst, keep a checked out working copy, regularly updated, and then 
rsync the whole thing to it's final destination, excluding the .svn/ 
folders.

Hope that helps !
François



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org