@terminhell@lemmy.dbzer0.com to Linux@lemmy.ml • edit-210 months agoWhy I dislike snapslemmy.dbzer0.comimagemessage-square85fedilinkarrow-up1343arrow-down124file-text
arrow-up1319arrow-down1imageWhy I dislike snapslemmy.dbzer0.com@terminhell@lemmy.dbzer0.com to Linux@lemmy.ml • edit-210 months agomessage-square85fedilinkfile-text
minus-square@Pantherina@feddit.delinkfedilink7•10 months agoRuntimes are okay, the problem is there is no runtime package manager and often you have like 7 of them, which is horrible. But on modern hard drives also no problem. Appimages cant be easily ran from terminal, you need to link then to your Path. For Flatpak I made a tool that aliases their launch commands to be very easy.
minus-squarejanAkalilinkfedilinkEnglish6•10 months ago Appimages cant be easily ran from terminal, you need to link them to your Path. On many distros “~/.local/bin” is already in PATH, that’s where I put my appimages, then make them executable and it just works.
Runtimes are okay, the problem is there is no runtime package manager and often you have like 7 of them, which is horrible. But on modern hard drives also no problem.
Appimages cant be easily ran from terminal, you need to link then to your Path.
For Flatpak I made a tool that aliases their launch commands to be very easy.
On many distros “~/.local/bin” is already in PATH, that’s where I put my appimages, then make them executable and it just works.