I don't think that would help, because the resulting .pkg file would still use the local copy of Installer.app on the client device. You would have to deploy a modified version of Installer.app on all clients, but then you would create the opposite problem, not to mention Installer.app constantly being modified as part of OS updates. You could create and Installer plugin that runs the uninstall, you would have complete control over that UI. But that's a lot of work for very little gain. Honestly, in my experience it really isn't an issue that the text is wrong. And as I've previously mentioned, as soon as you start presenting "uninstall packages" via Munki or Jamf Slef Service or something similar, it truly becomes a non-issue.
On Mar 29, 2017, at 5:35 PM, Stephen Kay <sk@karma-lab.com> wrote:
I'm wondering if it would be possible to edit an instance of the Packages app (i.e. edit the .nib files or .string files in the Packages.app/Contents/Resources) so that you had a version that you only use for creating uninstallers, where you fix the text to be more logical...
- Stephen
On 3/28/17 6:30 PM, "Conor Schutzman" <conor@mac.com> wrote:
Less than ideal, certainly, but doable. You have 2 sets of users, some won't read any of that stuff anyway (so likely won't even notice the confusing descriptions), and and those that will (who you can educate through a readme).
You can mitigate some of those issues through use of a software deployment tool like Munki, Jamf, or AirWatch, in which case the end user likely won't actually see the UI (as such tools present the installer through their own store interface and then execute it via command line).
On Mar 28, 2017, at 6:18 PM, Stephen Kay <sk@karma-lab.com> wrote:
I make a payload-free raw flat package.
I experimented a bit with this. The problem I see is that, even with making it a distribution and customizing the presentation using text files for the pane contents, assuming you name the .pkg something like Foo Uninstaller, you end up with cryptic messages that cannot be changed such as:
Title of Window: Install Foo Uninstaller "Welcome to the Foo Uninstaller Installer"
Installation Type: Standard Install "Click Install to perform a standard installation....
[Except this is an UNINSTALLER....]
Button: INSTALL
Password dialog: Installer is trying to install new software....
Button: Install Software
Summary: The installation was completed successfully (at top, cannot be replaced).
So it seems not an ideal method.... Unless I'm missing something...
Thanks, - Stephen
On 3/25/17 5:58 PM, "Conor Schutzman" <conor@mac.com> wrote:
I make a payload-free raw flat package. I use the "preinstall" script in Packages to script out a removal of the files my install package added (this obviously varies greatly by software title). I then use a "postinstall" script in Packages to script a 'pkgutil --forget" command for the package identifier of the install package.
On Mar 25, 2017, at 5:53 PM, Stephen Kay <sk@karma-lab.com> wrote:
(Sorry, reposting with correct title).
How does one write an uninstaller for a Packages installer?
Thanks, - Stephen
_______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/conor%40mac.com
This email sent to conor@mac.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com