options.bin should default to package.productName

What version of electron-installer-debian are you using? 0.7.1

What version of node and npm are you using? 6.12.0 5.5.1

What operating system are you using? Arch Linux (surprisingly works)

Can you compile the example app successfully? I can compile my own app.

What did you do? Please include the configuration you are using for electron-installer-debian. I didn’t use any special config besides src/dest/arch. I configured my app for electron-packager by having an npm-style package name in the name field (vivi) of my package.json, and a human-friendly name in productName (Vivi). This makes electron-packager rename the electron binary to the productName, not the name, i.e. Vivi-linux-x64/Vivi.

What did you expect to happen? The generated /usr/bin symlink to point to the renamed executable.

What actually happened? It points to vivi instead of Vivi, which is of course broken:

-rwxr-xr-x root/root  80394960 2017-11-20 00:42 ./usr/lib/vivi/Vivi
lrwxrwxrwx root/root         0 2017-11-20 00:42 ./usr/bin/vivi -> ../lib/vivi/vivi

I can set options.bin to Vivi, but it seems like it should default for me.

[malept]

Not sure if this helps your use case, but see: https://github.com/electron-userland/electron-packager/pull/758

[DuBistKomisch]

@malept It won’t help me now since I still want to keep it as Vivi on Windows/Mac, but this would have helped prevent the problem in the first place yes.