On 06/27/2010 09:58 AM, Aaron Maxwell wrote: > [0] In other words: suppose within local directory /src, there is a > symlink /src/A pointing to /something/A. Then "s3cmd sync --some-flag /src/ > s3://bucketname" would effectively behave as if you had first executed: > rm /src/A > cp -a /something/A /src/A > > Obviously, this would not be reversible across the corresponding "s3cmd sync > s3://bucketname /some/local/path" command.
I see, so you don't want to store the symlink itself but instead store the file the symlink points to. Hmm, that's a completely different story. I suggest you add --follow-symlinks parameter and then let [sync] and [put] upload the referenced files. Also make sure it safely skips (perhaps with a warning) over "broken symlinks", ie those that point to non-existent files. That should be a pretty straightforward feature add. You'll have to add an option at the option parsing section near the end of s3cmd, add a new flag to S3/Config.py and update manual page in s3cmd.1. And obviously modify the file upload code. Looking forward for your contribution :) Michal ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ S3tools-general mailing list S3tools-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/s3tools-general
