Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Hide progress/status window when pkg installer is running #288

Open
allenfisher opened this Issue · 6 comments

3 participants

Allen Fisher Kornel Matt Timmons
Allen Fisher

We have to run a pkg (don't ask) to run an update. The problem is, the status window in finish_install sits on top of the Installer window and can't be moved to the back. We still want our app to relaunch after the installer completes. I could just comment out the line that shows the window, but the code suggests that there might be a boolean to not show the interaction.

Is there a switch somewhere that I could use to hide that status window?

Thanks!

Kornel
Owner

I think the status window should always be hidden when running pkg installer.

Kornel pornel added the label
Kornel pornel changed the title from How to not show status window... to Hide progress/status window when pkg installer is running
Matt Timmons

Along with this, it may be wise to make the finish_installation app not re-open the app when finished. Leave that to the post flight script on the installer. Or at least allow the option.

Kornel
Owner

@MattTimmons that's surprising to me. Why would you prefer to relaunch the app from the pkg?

Matt Timmons

Hello sir, In some cases, I am creating a new app bundle name or location. For instance, I switched one of my apps to pkg update based just to force the app to live in the /Applicaiton spot and in the proper permissions. Lets say the originall app was on the users desktop for fun. They run the updater, the pkg script puts the final app in the /Apps folder... but then sparkle opens the original ~/Desktop app. I have a pre flight script now that removes the app from ~/Downloads , ~/Applications, but other locations could be dangerous to implements a removal.

Thus why I suggest this as an option. Thoughts?

Kornel
Owner

Thanks for the clarification. I see how it'd be useful, but on the other hand every feature has a cost of maintenance, documentation, etc.

Have you considered separating concern of updates with moving of the app? https://github.com/potionfactory/LetsMove/

Matt Timmons

Hi, I understand completely and would vote for what is best for most users. I have used LetsMove but have had problems with permissions at times.. See Issue #377 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.