On Tue, Feb 19, 2013 at 12:27:22PM -0600, John Sauter wrote: > In July-August of 2012 there was a discussion of the new meaning of the > --exclude qualifier. I was concerned that the new meaning meant that I > could no longer conveniently use S3cmd to backup the *.gpg files in a > wide and deep directory tree. I suggested that the new function of > --exclude should be moved to a new qualifier for compatibility. > > The URL for archive of the discussion is > <http://sourceforge.net/mailarchive/message.php?msg_id=29617785>. > > Has my concern been addressed? > John Sauter (john_sau...@systemeyescomputerstore.com)
It has not. The equivalent rsync command: $ rsync -a --exclude='*' --include='*.gpg' src dst copies nothing, as 'src' matches '*'. So the new behavior of s3cmd sync matches that of rsync, which I believe is what most users would expect. I believe what you are looking for is the rsync equivalent of: $ pushd src $ find . -name \*.gpg > ../files-from.txt $ popd $ rsync --files-from=files-from.txt src dst which copies only the files specified in files-from.txt which was created apriori to the rsync. Correct? If so, I think this could be added into S3/FileLists.py:_get_filelist_local() in a fairly straightforward manner. But it would still require you to change your script. Before heading down this path, I want to be sure my understanding is correct. Please advise. Thanks, Matt -- Matt Domsch Technology Strategist Dell | Office of the CTO ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ S3tools-general mailing list S3tools-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/s3tools-general
