Better Tarball Release for Linux #27

New Issue

kirsle · 2020-05-23T03:16:27Z

kirsle commented

2020-05-23 03:16:27 +00:00

Currently I package Doodle into .rpm and .deb files which install nicely and put a launcher icon in your app drawer and all.

But the tarball release is just a basic zip of the files.

Taking inspiration from Telegram, the stand-alone binary release could automatically install a launcher icon for itself into a user's app drawer.

Implementation ideas could be:

The binary checks its location on the filesystem.
If doodle is run from a path under the user's $HOME, run the install code.
- If the binary is outside $HOME, as in /opt/doodle or /usr/bin/doodle, then it was likely installed by rpm or deb and need not run this code.
Create a .desktop launcher in the user's ~/.local/share/applications folder.
- Point the executable path directly to doodle's current location, wherever the user extracted it to.

Currently I package Doodle into .rpm and .deb files which install nicely and put a launcher icon in your app drawer and all. But the tarball release is just a basic zip of the files. Taking inspiration from Telegram, the stand-alone binary release could automatically install a launcher icon for itself into a user's app drawer. Implementation ideas could be: * The binary checks its location on the filesystem. * If `doodle` is run from a path under the user's $HOME, run the install code. * If the binary is outside $HOME, as in /opt/doodle or /usr/bin/doodle, then it was likely installed by rpm or deb and need not run this code. * Create a .desktop launcher in the user's ~/.local/share/applications folder. * Point the executable path directly to doodle's current location, wherever the user extracted it to.

kirsle added the

wontfix

label 2022-01-24 04:58:01 +00:00

kirsle closed this issue

2022-01-24 04:58:04 +00:00

Sign in to join this conversation.