Archive creation scripts for new software update system We need to be able to create two types of archives: a full update and a partial update. Two scripts will be created with usage as follows: $ make_full_update.sh Usage: make_full_update.sh [OPTIONS] ARCHIVE DIRECTORY $ make_incremental_update.sh Usage: make_incremental_update.sh [OPTIONS] ARCHIVE FROMDIR TODIR These bash shell scripts depend on the following command line utilities: mar (bug 296303) mbsdiff (bug 296295) bzip2 is also required.
Created attachment 185095 [details] [diff] [review] v1 patch
Comment on attachment 185095 [details] [diff] [review] v1 patch There are some interesting things I don't understand, like "> $manifest", so if you want a detailed review you need to find someone else who knows shell scripting better than I (that's what perl is for!). My prototype scripts of a similar nature always added ".autoreg" to the update: is this the correct script to do this? Does the update system preserve mtime on files, in which case we might need a special "touch" command in the update manifest itself?
Shouldn't the change to app/gecko version/build-id be enough to trigger compreg.dat and xpti.dat to be blown away? So, maybe adding .autoreg is not needed? Right now the update system does not preserve mtime on files. I've often wondered if it should.