`--out` inconsistency about electron-packager

[malept]

Either Linux is the odd one out or Windows is. OS X is a special exception because of how Mac apps work. I'd argue that Windows is being weird - why does it need to be in a subfolder of the args.out folder?

[sindresorhus]

I think it's Linux, because if I don't specify a --out the content ends up in ./App-linux/.

[malept]

It makes sense to default to ./App-linux, so that it doesn't pollute the current directory. If args.out is always appended by /$APP_NAME-linux, that will make #33 more complex (i.e., having to rename that folder before packaging it up).

[junosuarez]

In conjunction with #40, I think the output folder should default to a combination of ./$APP_NAME-$PLATFORM-$ARCH

[jenslind]

I would prefer: ./out-folder/$PLATFORM/$ARCH/foo.app or ./out-folder/$PLATFORM-$ARCH/foo.app especially when running with --all

[englercj]

+1 Just hit this today, I like using platform/arch in the output folder. I agree with @jenslind I think ./out-folder/$PLATFORM/$ARCH/... is best, and ./out-folder/$PLATFORM-$ARCH/... is good.

[kfranqueiro]

Regarding which one is the odd one out, I'd also say it's Linux, for a couple of reasons:

• It doesn't use os.tmpdir() to do its work first like Win/Mac
• Whereas the Win/Mac scripts effectively do path.join(opts.out || process.cwd(), ...), the Linux script does opts.out || path.join(process.cwd(), ...)

[max-mapper]

I fixed the Linux inconsistency today in 86edff6, but leaving this open as there are some other good suggestions we can think about in the future