proposed export option
Hello, I'd like to add a new option to the export command that allows the user to export files only if the file size has changed--something like svn export --skipfilesmatchingsize The idea is to do a quick-and-easy, traffic-minimizing deployment of files that are unlikely to remain the same size when modified. I'm doing this as a project for a client who would like the change to be incorporated into a release version on Collabnet's website. I'm new to subversion development, and I'm looking for any advice or suggestions the developers here may have regarding the proposition. Thanks, Paul Breen
Re: proposed export option
Thanks for your reply, Ryan. On Mon, 4/26/10, Ryan Schmidt wrote: > Changed since when? Changed since the last deployment. The routine would send the file sizes of the files on the deployed computer to the repository server, and if the file sizes differed from the file sizes of the given revision (the current revision by default), the server would send the updated file to the deployed computer. > I think > you'll be better off using existing solutions to this > problem, such as rsync from a local svn export to your > remote deployment, or even simply making your remote > deployment a working copy and using svn update there. My client is aware of rsync utility, but would prefer to use svn. I'll have to correspond with her to find out why she doesn't want to use rsync. As far as making the remote deployment a working folder and using svn update, she doesn't want to have the clutter of the hidden .svn folders on the deployed computers. For anyone who's interested, the details of the project I'm working on can be found at www.rentacoder.com/RentACoder/misc/BidRequests/ShowBidRequest.asp?lngBidRequestId=1395905 Here my client gives the use cases for the feature she's looking for. I'll speak with her about the suggestions I got here and relay her responses on this mailing list. Thanks, --Paul Breen
Re: proposed export option
Hello, I previously inquired about adding a –skipfilesmatchingsize option to the export subcommand. I have implemented that feature, and I was wondering if it has any chance of making it into the trunk directory for svn. It currently has performance issues, and I don't want to spend a lot of time optimizing the code if it's never going to be incorporated into the main development line. If the feature is not acceptable as described in my previous message, could it be made acceptable if it were expanded somehow to make it of more general use? Maybe by using checksums instead of file size or, more ambitiously, I was thinking something like a rsync subcommand that allows a person to synchronize an unversioned folder with an svn repository. Any comments or suggestions would be greatly appreciated. --Paul Breen --- On Mon, 4/26/10, Paul Breen wrote: > From: Paul Breen > Subject: proposed export option > To: users@subversion.apache.org > Date: Monday, April 26, 2010, 11:07 PM > Hello, > > I'd like to add a new option to the export command that > allows the user > to export files only if the file size has > changed--something like > > svn export --skipfilesmatchingsize > > The idea is to do a quick-and-easy, traffic-minimizing > deployment of > files that are unlikely to remain the same size when > modified. I'm > doing this as a project for a client who would like the > change to be > incorporated into a release version on Collabnet's > website. I'm new > to subversion development, and I'm looking for any advice > or > suggestions the developers here may have regarding the > proposition. > > Thanks, > > Paul Breen >
