• arya@lemmy.ml
    1·
    4 hours ago

    I installed Rocky linux on my new server instance today and I found out that vnstat is not available as a package in the repos. It used to be available on the older versions. 😭 It’s been a while since I got back to Linux for my personal use.

  • ohshit604@sh.itjust.worksEnglish
    3·
    9 hours ago

    When the dependencies need dependencies and then those dependencies need dependencies, the rabbit hole is endless!

  • Hemingways_Shotgun@lemmy.caEnglish
    9·
    11 hours ago

    I honestly can’t remember the last time I’ve come across a package that I needed that so obscure that it wasn’t found somewhere as at the very least an appimage, if not a flatpak. I haven’t had to build from source in I don’t even know how many years now.

    • Ibuthyr@lemmy.wtf
      5·
      9 hours ago

      Try making music on Linux. You’ll be compiling obscure shit and tweaking configs all the time.

      • Hemingways_Shotgun@lemmy.caEnglish
        3·
        8 hours ago

        True. But I was coming at if from the perspective of an every day user coming from Windows. email, word processing, internet, etc… Even gaming and photo editing.

        The more professional the needed software gets, of course the more obscure it gets.

    • dodos@lemmy.world
      1·
      9 hours ago

      I think it depends on the distro. Nixos is pretty bad for this if you want to try out a project that is really new. If you wait a month or two a flake usually comes out somewhere.

  • Friendly Chemist@infosec.pub
    4·
    13 hours ago

    make: error: libX11.so permission denied or not found make: failed, something something finishing remaining jobs.

    dear god what does it mean

    I get that your issue was probably more nuanced than that, but what’s so confusing about inatalling missing build dependencies? If projects have a build guide sometimes they’ll straight up give you an install command for your distribution. If not, it’s up to you to find the package names corresponding to what you need to install since they can differ from distro to distro.

    • SparroHawc@lemmy.zip
      1·
      4 hours ago

      I wish Lemmy was able to have emoji reactions to comments just so I could react with a horrified face to this comment.

      In lieu of that, I’ll just have to put it here: 😱

    • da_cow (she/her)@feddit.orgOP
      2·
      12 hours ago

      If it would be that easy. The problem I had was, that I installed a dependency using my package manager, but to compile my originally wanted software I had to provide a cmake file (of the dependency I installed via my package manager) to the compiler, which I of course did not have.

      • Miaou@jlai.lu
        1·
        4 hours ago

        This often comes with the *-dev version of the dependency. The normal one contains the binaries, the dev version includes headers and often the FindPackage

  • UnityDevice@lemmy.zipEnglish
    4·
    16 hours ago

    More like:
    No system package -> installing from user repos -> appimage -> flatpak -> creating your own package -> using a VM with a distro that has the package -> not installing package

    If after that you still don’t have it, it wasn’t meant to be it’s probably just not very good software.

    • lilith267@lemmy.blahaj.zoneEnglish
      1·
      4 hours ago

      Personally go: Flatpak (I like easily controlling an apps premissions) -> flatpak version is broken… Try system package -> distrobox -> compiling -> appimage -> not installing a package

      Distrobox/containerd is so nice since a lot of the niche tools I use require Debian or Ubuntu dependency versions, but I’d be lying if I said everything “just works”

    • RustyNova@lemmy.world
      4·
      13 hours ago

      TBH if it’s just for that I’d rather use nix packages. But flatpak’s sandboxed app are better for sus packages or proprietary-might-spy-everywhere packages.

      • wheezy@lemmy.ml
        6·
        18 hours ago

        I rarely encounter them. But they usually work when I do. But, ugh, they’re just kinda gross. Like, is this a .exe? No thank you. Don’t give me windows trauma.

        • Damage@feddit.it
          1·
          10 hours ago

          I’m always like, “well, now where do I put this executable?”

          But they do work

          • wheezy@lemmy.ml
            1·
            5 hours ago

            Clearly in $HOME/Downloads/ and forget that you left it there. Then use app(3).AppImage the next time when you redownload it. Keeps you running the most up to date version. It’s flawless.

    • wheezy@lemmy.ml
      3·
      18 hours ago

      I’ve had the opposite experience with flatpaks that I have with snaps. I don’t really use them much. But when I see that as an option I use it and it just works. Definitely a fan as a USER of them. I’m sure people have their complaints as users and developers. But I definitely have to say it’s been positive so far. Which is a rare consistency in the life of installing packages.

    • NaibofTabr@infosec.pubEnglish
      28·
      1 day ago

      Flatpaks are better than Snaps, but properly maintained dependency trees and SBOMs are best, by a wide margin.

  • palordrolap@fedia.io
    20·
    1 day ago

    Last week was the first time I think I’ve ever got a random Internet tarball to configure, make and make install. Program even did what it was supposed to too. I was amazed.

    • rozodru@piefed.socialEnglish
      2·
      13 hours ago

      nix-shell is great too. sort of like a “demo” of something before actually committing to it or if you just want to use something one off without adding it to your config and rebuilding.

      As a dev it’s fantastic for testing also. can just try something on a bunch of browsers without actually installing the browser. love it.