Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move to Applications folder #19

Open
RamonGilabert opened this issue Oct 1, 2018 · 3 comments
Open

Move to Applications folder #19

RamonGilabert opened this issue Oct 1, 2018 · 3 comments

Comments

@RamonGilabert
Copy link
Collaborator

Is it hard to do something like this:

screen shot 2018-10-01 at 10 46 32 am

I think it's a nice touch. But we might not need that. What do you think?

@zenangst
Copy link
Owner

zenangst commented Oct 6, 2018

Gonna investigate how to create dmg files. Should be fairly straight forward. However, I think it would be nicer to invest some time in automatic updates. As in, the app downloading a new version of itself and handling relaunching etc.

@zenangst
Copy link
Owner

zenangst commented Oct 6, 2018

We could have both, dmg for new installations and a zip-file for updates ;)

@JayBrown
Copy link
Collaborator

JayBrown commented Nov 14, 2018

Apple encourages the use of DMGs, and they have their advantages, not because of volume design, but because they can be code-signed for secure distribution. There are good tools for this, incl. DMG layout design, like DropDMG. And it's probably pretty easy to rely solely on DMGs, for first installation and updates. (DMGs can be quietly mounted on any mount point, which is a big plus; just mktemp, then hdiutil with quiet mount arguments, and let the updater do the job, Sparkle etc.)

[Deleted comments about .pkg, because you shouldn't use them to install into ~/Applications.]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants