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

Re: Export entire changed files for zip patch

From: Scott Pederick <scott_at_solidstrategies.com.au>
Date: 2007-06-28 12:48:40 CEST

Hi Nathan,
> just guessing a bit; as i havent used this myself; but isnt this what
> patch <http://en.wikipedia.org/wiki/Patch_%28Unix%29> is for?
> basically the flow here is to diff the to repositories; dump the diff
> of each file in the repo to a diff file.
> then recursively apply the diff files to the target source base using
> patch.
> you would still need to handle adding new files and removing deleted
> files though.
The problem is I can't use patch - the app is stored as php source and
is only accessible via ftp. The only way to upload it is to upload each
of the files that have changed. Rather than having to lug around the
entire revision, I want to be able to package up just the changed files
in an archive. You this extract the archive, upload it over the top of
the existing source since the directory structure is maintained and the
web app is patched.
> in order to get a listing of the files that have changed between 2
> components of the repository (typically a development branch and the
> trunk)
> svn diff -x -w svn+ssh://user@repohost/trunk
> svn+ssh://user@localhost/branch-wc | grep '+++'
> svn diff -x -w svn+ssh://suer@repohost/trunk
> svn+ssh://user@localhost/branch-wc | grep '\-\-\-'
> so, in my mind i would start out by using those commands to generate a
> list of files then iterate over the list producing the diff files.
> note here, im assuming the diff output from svn is compatible w/ gnu
> diff (because thats what patch takes as input).
> you will have to have some client-side script to handle the merging;
> no matter what the implementation, so
> if you are deploying the php to windows and unix(ish) machines you
> will likely have to maintain separate scripts for both platforms.
> why not just use a tagging approach and push out revisions of the
> source? i think this would be a more direct solution and very easy to
> implement.
> also, i think tagging is more in tune w/ the svn way of facilitating
> sdlc (imho).
Not sure what you mean by this but that probably has more to do with my
understanding of svn. Even if the release is tagged, it doesn't make it
any easier to get the list of changed files but just a different
checkpoint to generate a "patch" (ie. archive of changed files) against.

Sorry if I haven't understood entirely what you meant but the main
problem is that I only have ftp access to these shared hosting
environments. Thanks for the reply.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 28 12:49:39 2007

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.