Rainer Meier <r.meier at wpkg.org> writes: > Well, currently I have limited access... but in general you might either > use simple 'copy' or 'xcopy' to copy/overwrite the file or you might > prepare a self-extractor archive (e.g. 7-zip self extractor) and just > add it as an install/upgrade command. > > Personally I am using a set of install helper scripts (unattended.cmd, > unattended-postinstall.cmd...) and I would simply add a copy command to > the unattended-postinstall.cmd script in this case. Use the mailing list > archive to find listings of these scripts I posted recently. [...] Personally I split the firefox xml in 3 steps: - One to install it - One to configure all.js (echo the general.config.filename stuff, check with a grep) - One to copy the config and set some reg keys. So the configuration is put back if someone change it without the need to re-install firefox. By the way, I use a file size check for the config to see if it changed (for upgrade for example), any plan to add some md5/sha check to wpkg ? Regards. NB: I plan to publish my .cmd files as soon as I have the agreement of my employer. -- Daniel Dehennin RAIP de l'Orne |