From: Michal L. <mi...@lo...> - 2008-06-23 15:54:42
|
Hi everybody! S3cmd 0.9.8 is out :-) The main change since 0.9.7 is a support for excluding files from 'sync'ing. Several new options have been added: The most obvious one is --exclude that expects a shell-style wildcard pattern as its argument. I.e. to exclude all files with ".tmp" extension use s3cmd sync --exclude '*.tmp' {from} {to} Sometimes you'll need a large number of patterns for exclusion. Instead of having them all on the command line save them to a {file} and then have s3cmd read them with --exclude-from {file} Shell-style wildcards are well known by all sysadmins. Occasionally they are not powerful enough and some patterns may be impossible to express. In that case you'll want to use --rexclude and its counterpart --rexclude-from options that expect a Regular Expression instead of Shell-style wildcard pattern. Note that you can use all these four options on the same command line together and any of them can be used as many times as you want. I.e. having s3cmd sync --rexclude-from {file} --exclude {pattern} {from} {to} is perfectly ok. Since getting the patterns right may be tricky, especially with RegExps, you'll want to give --debug-exclude option a try from time to time. It'll tell you what file names are excluded and which pattern caused it. s3cmd exits after the matching phase and won't transfer any files to/from S3. Minor improvements in 0.9.8 include: - regained compatibility with Python 2.4 - better checking of bucket names to follow S3 rules - s3cmd can now run from system scripts without having $HOME env variable set. Download it from here: https://sourceforge.net/project/showfiles.php?group_id=178907&package_id=218690 There are no *known* bugs that should prevent you from using the program. Which means: if it crashes or fails to work in any way *LET ME KNOW* That's the only way to get it fixed in the next release. If I wouldn't know it doesn't work I won't fix it. Thanks heaps ;-) Enjoy :-) Michal |