Tyler J. Wagner wrote at about 07:27:30 +0000 on Wednesday, November 4, 2009:
 > On Wednesday 04 November 2009 04:59:21 Jeffrey J. Kosowsky wrote:
 > > It would be great to be able to add conditions based on the other
 > > basic file attributes known to BackupPC, including create/modification
 > >  date, size, permissions, file type, and perhaps also more flexible regexp
 > >  matching on the filename.
 > 
 > That would be an issue with the rsync client.  We can do whatever we want on 
 > the server, but on the client end we can only do what rsync can do.  As an 
 > administrator I am not interested in installing client software or even a 
 > patched rsync.  I'm so glad checksum-seed in now in rsync trunk!
 
Not true! Perhaps you didn't read (or at least quote) the rest of my
post which explained how it would all be done on the *server*, where
*after* files were transferred using the normal (untouched) transport
method, a single (potentially) compound Perl conditional statement
would be applied against any file matching the modified
include/exclude statement to determine whether or not to indeed add it
to the new file list. No conditional would be applied if you just
wanted to use the standard include/exclude logic.

In particular, again, there would be *no* change to the client or to
the transport method. In fact, the change would probably require only
a couple of lines of code in total. First, a couple of lines of code
to parse the modified config syntax and then a couple of lines to
apply the test to files just before they are passed on to the new file
list.

I will repaste the rest of my original post to supply the details....

Jeffrey J. Kosowsky wrote at about 23:59:21 -0500 on Tuesday, November 3, 2009:
 > For includes, this would be simply implemented as an additional test
 > after the files has been transferred over (which would still be based
 > on the generic includes statement) and before it is added to the New
 > File list.
 > 
 > For excludes, you would have to allow the transfer over of all
 > possible candidates and only exclude them once they are transferred
 > over based on the additional supplied logical conditions.
 > 
 > The easiest way to implement this would be to allow an arbitrary perl
 > condition based on a fixed set of primitives. These primitives would
 > return the file name (full path and basename), size, mod/creation
 > dates, ownership, and permissions.
 > 
 > The idea would be to associate an (optional) potentially compound test
 > with each include/exclude item.
 > 
 > It would be a bit harder to implement a GUI interface and it probably
 > would be limited to a subset of all possible logical conditions. One
 > could think of doing something similar to how Excel allows multiple
 > conditions for conditional formatting.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/