Text rewritten for better clarity

diff --git a/pkg resources/multi-binary scripts/readme b/pkg resources/multi-binary scripts/readme
index 7938b28..3f6e683 100644 (file)
--- a/pkg resources/multi-binary scripts/readme
+++ b/pkg resources/multi-binary scripts/readme
@@ -32,4 +32,4 @@ These multi-binary pre/postinstall scripts are unfinished, and indeed now lack f
 
 The intent was to compile multiple single-architecture binaries targeting each OS X release then detect the target OS X version and processor architecture at install time, copying into place only the one necessary binary. The benefit of this approach would be one single installer package for ALL OS X versions and reduced cruft on the target machine.
 
-They are left in the project as the basis for potential future development, but would need to have only their unique parts merged into the latest version of the single-binary scripts.
\ No newline at end of file
+They are left in the project as the basis for potential future development, however their sole unique feature is unrelated to multi-binary support (indeed the single-binary scripts should be used as a starting point for any putative multi-binary support). The unique feature is in postinstall and is programmatic replacement of the package identifier in the uninstall script, thereby handling whatever pkg id is entered into the Packagemaker project. As things stand this replacement is instead handled by constructPkgContent.sh, which can only change the version number and therefore restricts the format of the package identifier string.
\ No newline at end of file