Normally, this feature request would be added as part of the repository discussions, but for now it will be posted here.
So, I migrated to sway on Kali Linux, and wanted to give this project a spin. Kali has a lot of menu entries built-in to run its numerous tools, and in sway these menu entries were missed. So here is how the installation process looks at this minute.
To install: onagre --> there is a dependency --> pop-os/launcher
To install: pop-os/launcher --> there is a dependency --> casey/just
To install: casey/just --> there is a dependency --> prebuilt-mpr
To install: prebuilt-mpr --> an additional repository has to be added to /etc/apt/sources.list.d
We have all played the game of "find the dependency", and often this game does involve hunting down source code and manually compiling it, but this is a little much to test out a graphical menu. Couldn't the required portions of pop-os/launcher just be included in the project? Or couldn't an installation script be written to automate this process?
I just scrolled down and found where just offers prebuilt binaries, so it isn't as tedious as I previously thought. Regardless, something more independent and standardized might be worth considering.
Normally, this feature request would be added as part of the repository discussions, but for now it will be posted here.
So, I migrated to sway on Kali Linux, and wanted to give this project a spin. Kali has a lot of menu entries built-in to run its numerous tools, and in sway these menu entries were missed. So here is how the installation process looks at this minute.
To install: onagre --> there is a dependency --> pop-os/launcher To install: pop-os/launcher --> there is a dependency --> casey/just To install: casey/just --> there is a dependency --> prebuilt-mpr To install: prebuilt-mpr --> an additional repository has to be added to
/etc/apt/sources.list.d
We have all played the game of "find the dependency", and often this game does involve hunting down source code and manually compiling it, but this is a little much to test out a graphical menu. Couldn't the required portions of
pop-os/launcher
just be included in the project? Or couldn't an installation script be written to automate this process?I just scrolled down and found where just offers prebuilt binaries, so it isn't as tedious as I previously thought. Regardless, something more independent and standardized might be worth considering.