I ended up using msi2xml to unpack the MSI, replace the krb5.ini with Penn's, and repack the MSI.
It worked like a charm. :) • http://stackoverflow.com/questions/126562/how-to-replace-a-file-in-a-msi-installer • http://msi2xml.sourceforge.net/ > On Feb 4, 2015, at 3:09 PM, Benjamin Kaduk <[email protected]> wrote: > > On Wed, 4 Feb 2015, Matt Miller wrote: > >> Hi, >> >> We want to distribute a "Pennified" KfW installer with a custom krb5.ini >> file. What's the recommended way to do this? I can think of two possible >> ways; >> >> 1. unpack the MSI, replace the krb5.ini file, repack. >> 2. use a wrapper to install default MSI, then copy our krb5.ini into place. >> >> But I can't find any documentation on customizing the installer, so any >> help would be appreciated. > > We have an "MIT-ified" installer that we distribute within MIT; there is a > little bit of code in the installer generation to help with this. > > https://github.com/krb5/krb5/blob/master/src/windows/installer/wix/config.wxi#L69 > makes the installer pull the configuration files (just krb5.ini at the > moment) from the "athena" subdirectory instead of using the default. You > could add a local patch to do a similar thing for Penn, but that would > require building (and signing) your own installers. > > I don't remember whether orca provides an easy way to effect a change of > this nature, but it is certainly a useful tool for MSI inspection and > modification. > > -Ben -- Matt Miller ISC/Cient Care phone: 215-573-3829 University of Pennsylvania jabber: [email protected] _______________________________________________ kfwdev mailing list [email protected] http://mailman.mit.edu/mailman/listinfo/kfwdev
