• ArcaneSlime@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      2
      ·
      3 hours ago

      Thanks! The “having to figure out dependency management” thing has been the largest roadblock in me trying out Slackware so far, but I really do want to try it.

      • mech@feddit.orgOP
        link
        fedilink
        arrow-up
        2
        ·
        2 hours ago

        If you install it the recommended way (full installation) all of Slackware’s dependencies are taken care of.
        Additional software comes from Slackbuilds or compatible community repos. They include dependency info and helper programs that resolve dependencies for you.
        No one is masochistic enough for the old method of “compile till it errors out, look for missing libraries in the logs, try to compile those, repeat”.

        • ArcaneSlime@lemmy.dbzer0.com
          link
          fedilink
          arrow-up
          1
          ·
          2 hours ago

          Yeah I’m sure I would do the full build, but also I’m definitely a weirdo and there’s no way any of the shit I use comes stock lol so it has been mainly the “additional software” and dependencies bit, and to be honest I had no clue how you guys did it but this post helped a lot, thanks!

          I’m still kind of a linux noob is also the thing, I started my journey years ago, but only by booting into tails every so often, then eventually ~4y ago I installed Fedora, eventually got tired of gnome and when the framework 16s dropped I grabbed one and switched to FedoraKDE, and that’s it, I haven’t made the jump to a big boy distro that “isn’t recommended for beginners” but Slackware will be the one I try, because I was a SubGenius before I even installed linux.