DISCLAIMER: Arch Linux is not a beginner friendly distribution, and this is not a recommendation or good practice.

I know how to use pacman -S. I have yet to experience a Discover related issue after months of use.

  • Speiser0@feddit.org
    2·
    19 hours ago

    Eh, it’s a teensy bit harder, since you have to remember what -S means, rather than the easy to remember and plain English ‘install’. But, yeah, not much of a difference.

    Thanks! I initially thought about writing this in my comment in parentheses, but then didn’t do because it would’ve made the comment longer, and I’m not sure if other people want to read the pedantic truth anyways. I’m glad you filled this void.

    The instructions for installing on ubuntu only work because of ubuntu’s popularity. Also if you can copy-paste commands, you can also just follow build instructions. In arch, these commands are in the PKGBUILD, you don’t have to copy them manually. Plus you have the knowledge that you’ll have something that you can also deinstall later. Applications’ websites usually don’t have uninstallation instructions.

    • OwOarchist@pawb.socialEnglish
      2·
      18 hours ago

      I’m not sure if other people want to read the pedantic truth anyways. I’m glad you filled this void.

      Glad my pedantry could be of service, lol!

      The instructions for installing on ubuntu only work because of ubuntu’s popularity.

      True, but this is still a very real effect with real-world benefits.

      (And I wouldn’t necessarily say it’s just Ubuntu’s popularity. More like, due to Debian and Debian derivatives’ popularity, of which Ubuntu is one. Since there are so many popular distros out there that are Debian-based where Debian-style install instructions will work (and quite a few people running Debian itself), it makes sense to give Debian-style install instructions first.)

      Also if you can copy-paste commands, you can also just follow build instructions.

      In my experience, not so much.

      Because even if you follow the instructions exactly, you’ll always run into some problem due to your build environment not being quite identical to the developer’s build environment, some library being half a version number off, and then cmake fails with a cryptic error message. So then you downgrade that library to the older version and try again, and this time it fails with a different cryptic error message that you can’t make any sense of at all this time, or the compiler quits because it says the code is formatted improperly on line 1437 and now you’re left wondering whether it’s an issue with your compiler or whether you should go in and edit the source code yourself to try and fix that supposed formatting error…

      I don’t know… I’ve tried this approach a few times – usually as a desperate last resort – and it never seems to actually work. In theory, it should. In practice … good fucking luck.