http://bugzilla.wpkg.org/show_bug.cgi?id=95
--- Comment #5 from Falko Trojahn <[EMAIL PROTECTED]> 2008-01-14 14:55:49 --- Reg. #3: http://wpkg.org/WPKG_flags#Rarely_used_parameters use wpkg.js /config:anotherconfig.xml and/or /base:path-to-newer-xml-and-files Reg. #4: why do you have a remove command in your package if you don't want the files to be removed? Any time later you can introduce a newer revision with a remove command if you really want to remove the files - since the update is made before removal since http://bugzilla.wpkg.org/show_bug.cgi?id=79#c42 If I understand you right, Tomasz, you could do the following: - have a location with the original 2GB contents and a corresponding package#1 which does rsync -a --delete source target or robocopy source target /mir - have a location with the files different to the original 2GB content and a corresponding package#2 which does rsync or robocopy to the same target as package#1 but without deleting (if you want to delete files, you would have to specify them in another install/upgrade cmd) So you can have several clients with original package#1, other clients with additional package#2. You can even have a "remove-only" package#3. But for this case I miss a check "if missing file ..." -> install the package (install cmd in this case removes the 2GB of course). Perhaps one could use something like logical "not", didn't check this (http://wpkg.org/Logical_tests). -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. ------------------------------------------------------------------------- Easy Software Deployment >> http://wpkg.org _______________________________________________ wpkg-users mailing list [email protected] http://lists.wpkg.org/mailman/listinfo/wpkg-users
