It’s not about the destination, it’s about the journey.

  • 0x4E4F@sh.itjust.worksOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    9 months ago

    Mhm. The exact same reason why I would recommend them to anyone that actually wants to know how Linux works, the dos and donts (like why having 2 or more package managers is a REALLY REALLY bad idea).

      • 0x4E4F@sh.itjust.worksOP
        link
        fedilink
        English
        arrow-up
        3
        ·
        edit-2
        9 months ago

        No, just a bad experience trying to actually run 2 of them on the same system. One was the main, the other was supposed to “patch” what the first one lacked… and then I realized that compiling from source and packaging with the original (first) package manager is a lot less painful than trying to juggle with both of them.

        • QuazarOmega@lemy.lol
          link
          fedilink
          arrow-up
          1
          ·
          9 months ago

          Oh that’s what you mean. I’m wondering, what did you do to be able to use 2 at the same time?

          • 0x4E4F@sh.itjust.worksOP
            link
            fedilink
            English
            arrow-up
            3
            ·
            edit-2
            9 months ago

            Well, you just set the second to ignore all inconsistencies regarding libraries and binaries from the first one. It sounds easier than it is to actually put in practice 😂.

            I was just experimenting, trying to see if the trouble is worth it… it’s not. Way too many ways to still fuck up your system… and I eventually did 😂. Luckily, I use BTRFS with snapshots, so no harm no foul, I just rolled back everything from the day before I decided to install the second package manager.