GeezerVison

Amazing, this is a great contribution @remixz, I'll try and make time to test this out and give feedback.

Initial quesitons:

1. is it possible to bring this on par to the Windows installer and make the node symlink an optional part of the install (opt-out)? We could perhaps do the same with npm so you could choose to not even install that, but that's arguably less useful.
2. should we include the license as rtf? part of the Windows installer build process is to make an rtf version (see vcbuild.bat), is there any reason to do the same here?

1. Yes! I'll have to add a flag or something to disable the symlink in tools/install.py so the node symlink isn't included in the installer, but otherwise it's easy to do. It'll just be an empty install step with a post-install script. I can also make the installer show the "custom install" view by default, so it looks something like this:
   
   As well, with the PR as it is, npm can be unselected, but it's still installed with the io.js step. This actually does beg the question: why is there a separate step for npm? From what I can tell, it's not needed.
2. We can add it as rtf, but there's no advantage I can think of, aside from changing the font.

Idea: Should this include an uninstaller? Choosing the option would disable all the others, like this:

Then it can just run an arbitrary script that would remove files. This would help bring parity with other platforms.

I think an uninstall is important.

is it possible to bring this on par to the Windows installer and make the node symlink an optional part of the install (opt-out)?

I'm not sure if that makes sense on OS X. A symlink opt-out may give the false impression that joyent/node and io.js can coexist peacefully when they can't.

The installer installs to /usr/local. If a joyent/node install already exists there, io.js will happily stamp on it. The symlink is just the top of the ice berg.

The only scenario that I can think of where an opt-out would help is when joyent/node and io.js are installed to separate locations that are both on the PATH. The exact meaning of the "Create a symlink" checkbox would need to be called out in the installer if we don't want angry bug reports. :-)

@bnoordhuis A description can be added to the symlink installer entry, so when someone clicks on it to uncheck it, it can say something like "joyent/node and io.js don't coexist nicely, keeping this symlink is recommended".

@remixz Sounds good.

Could we reuse the translations for other distributions?

I prepared the German translation for the installer using Packages: https://github.com/fhemberger/io.js/commit/65ba54ec0eb112ce040415ac2b3b321b8e38b5d1
As soon as this PR lands, we can use this commit as a basis for further internationalization.

@tellnes It's likely, but there'd have to be some changes so that it doesn't specifically reference Mac locations.

@fhemberger Awesome!! 👍 🎉 It might need to be rebased by the time this is merged, since the file will probably change a bit when the uninstaller is finalized, but this is great.

@bnoordhuis Implemented all of your changes. Thanks!

LGTM but I'm not an expert when it comes to OS X installers.

@iojs/collaborators Can I have one more LGTM?

@bnoordhuis Ah, I need to finish the uninstaller portion before this can ship. (unless you want to move that to another PR?)

Cool. I've added the uninstaller, which means once reviewed, this should be good to go.

From running local tests, it looks like tools/osx-codesign.sh may need to be updated. It tries to explicitly codesign node instead of iojs

Ah nevermind, got it to work. Is there a way to change the success screen when uninstall is selected? Currently, it is the same, which could cause some confusion.

This is what is shown after a successful uninstall:

@evanlucas I changed tools/osx-codesign.sh to sign iojs, since even though you got it working, I'm pretty sure it should be signing iojs, unless someone has a reason for it not to.

For the success screen, I'm pretty sure it can't change based on what's installed, which definitely leaves a sucky experience for people doing an uninstall.

i18n changes pending resolution of #819

Is the updated installer ready to land?

As #819 seems to be resolved according to the TC meeting, I'd love to add the translation for the installer and make it a proper PR.

Should /usr/local/lib/node_modules/ be removed?

I don't know if it's possible to implement this but what tools/install.py does is unlink the directory iff it's empty after removing all installed files.

@bnoordhuis Yup, that can be done! Added with 2526e1d.

@fhemberger If the translation issue is all resolved, then I think this is ready to land.

Thanks, I'll create a proper translation PR for further discussion as soon as this has landed.

@remixz We should add a paragraph to introduction.rtf to clarify that node.js and io.js cannot be installed in parallel (and the symlink will overwrite the one of any previously installed node versions). If the user wants to use both, they have to use version managers like nvm or n and use them instead of the Mac installer (see discussion in #389).

Any news on the status of the new Mac installer? cc @nodejs/core

@nodejs/collaborators Anyone familiar with the existing OSX installer that can review this?

On my list but not a high priority compared to other things like node-gyp, so help from others would be greatly appreciated. @remixz if you have time would you mind rebasing on the current master, there's been a bunch of changes in this area that you'll need to catch up on.

@remixz would you mind having another look at this, rebase and target a new PR against next for now and we might try and do this at the same time as #2247. It's not a top priority but would be good to get this done before the converged release.

I think we should definitely try to get this merged before the converged release. Anything I can do to help?

The changes in this PR need to be merged against the current master for the 4.0.0 release, including the renaming from 'iojs' to 'node'. It would be great if we could get this running, so we can ship localized installers in the next major version.

I did a rebase against master in #2571, can you all please have a look?

Closing this in favor of #2571