|
|
|
|
|
by tehbeard
1379 days ago
|
|
Yes it does? If it doesn't matter, why are there two or even 3 options at times for the same software with little detail as to why? And if the packaging difference does matter (as it did for my vlc issue, one solution only worked for the deb), then an explanation for newbies should be given as to the general expectations for each package type. Or should I just "git gud" and go digging through ppa/flathub? mailing lists to find a 2013 reply to a post? |
|
Like for example I've been playing with Kodi and as a deb package you can't install some (but not all) add-ons through the built in UI, you have to go find special apt packages for them and install those outside the Kodi UI. Nowhere is this documented or visible to users--Kodi's webpage doesn't concern itself with how Debian packages it so no mention there, and Debian itself is a black hole of information for end users. The exact same issue is present with RetroArch and its Debian packages version. My bottom line is I always pick a deb package as the very last option and expect pain or confusion when doing so.