How do you guys get software that is not in your distribution’s repositories?

    • ILikeBoobies@lemmy.ca
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Rpg paper maker

      Though the Linux version is now in a “do not use” state. The developer decided to just make it into a web app because it was only working on Ubuntu

      • cm0002@lemmy.world
        link
        fedilink
        arrow-up
        15
        ·
        1 year ago

        Clearly we need an Arch version of rule 34 and rule 35

        Rule 34a: If linux software exists, it’s in the AUR. No exceptions.

        Rule 35a: If linux software is not in the AUR, it will be made available in the AUR.

        • ulterno@lemmy.kde.socialBanned
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          I don’t intend on pushing that one to the AUR. It’s not worth it.
          Maybe I’ll make an AppImage at most.

          I don’t know any formal requirements for it being on AUR, but I just feel like this one does not fit there.

  • BigDanishGuy@sh.itjust.works
    link
    fedilink
    arrow-up
    40
    ·
    edit-2
    1 year ago

    Why not just stick to what we’ve always been doing?

    1. wget something.tar.gz
    2. tar something.tar.gz
    3. man tar
    4. tar xzf something.tar.gz
    5. cd something
    6. ls -al
    7. ./config.sh
    8. chmod +x config.sh
    9. ./config.sh
    10. make config
    11. Try to figure out where to get some obscure dependency, with the right version number. Discover that the last depency was hosted on the dev’s website that the dev self-hosted when it went belly up 5 years ago. Finally find the lib on some weird site with a TLD you could have sworn wasn’t even in latin characters.
    12. make config
    13. make
    14. Go for coffee
    15. make install
    16. SU root
    17. make install
    • merthyr1831@lemmy.ml
      link
      fedilink
      English
      arrow-up
      11
      ·
      1 year ago

      I much prefer our modern package format solutions:

      1. sudo apt install something
      2. open
      3. wtf this is like 6 months old
      4. find a PPA hosted by someone claiming to have packaged the new version
      5. search how to install PPAs
      6. sudo apt <I forgot>
      7. install app finally
      8. wtf it’s 2 months old and full of bugs
      9. repo tells me to report to original developer
      10. report bugs
      11. mfw original dev breaks my kneecaps for reporting a bug in out of date versions packed with weird dependency constraints they can’t recreate
    • PenisDuckCuck9001@lemmynsfw.com
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      We should normalize programs that don’t use such exotic and impossible libraries that you have to do anything besides type “make” and “make install” for it to work.

      In theory it’s a no brainer. In practice not so much.

  • cley_faye@lemmy.world
    link
    fedilink
    arrow-up
    40
    arrow-down
    2
    ·
    1 year ago

    Native package manager > Native binaries > AppImage > Flatpak.

    Yes, snap isn’t even on the scale.

    • Kusimulkku@lemm.ee
      link
      fedilink
      arrow-up
      39
      arrow-down
      1
      ·
      1 year ago

      Not a fan of AppImages myself. For an universal format it has surprising amount of issues with different distros, in my experience. And the whole Windows style “go to a website, download the AppImage, if you want to update it, go to the web page again and download it again” is one thing I wanted to get away from. At least they don’t come with install wizards, that clicking through menus thing was a pain.

      For one off stuff I run once and never need again, AppImage is alright. But not being built-in with sandboxing, repos, all that stuff, it just seems like a step back.

  • LainTrain@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    17
    arrow-down
    1
    ·
    1 year ago
    1. Compile from source
    2. Find alternative
    3. Deploy in VM/Docker

    If I wanted snap, flatpak or appimages, I would use windows. Shared dependencies or death.

      • LainTrain@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        1
        arrow-down
        3
        ·
        1 year ago

        I don’t like middle grounds in my packages, what can I say.

        Docker containers are treated as immutable and disposable to me, like a boot CD, for each, I write a shell script to generate both a .conf if needed, a docker-compose.yml and run the container.

        They’re plug’n’play separate parts to the rest of the OS, while packages are about integrating nicely with the rest of the OS, in a non-snowflakey, non-disruptive manner.

        I also hate .conf.d folders and always deleted them. One program, one .conf.

  • boredsquirrel@slrpnk.net
    link
    fedilink
    arrow-up
    14
    ·
    1 year ago

    Appimages are crap too, but at least there is progress with AppMan, repos and that sandboxing solution.

    Snaps are only sandboxed with Apparmor and snapd only allows a single repo (which contained malware multiple times) so get the hell off my lawn XD

  • Dop@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    1 year ago

    Linux noob here, can someone ELI5 why snaps are bad? And how does .deb works?

    • Lettuce eat lettuce@lemmy.ml
      link
      fedilink
      arrow-up
      12
      ·
      1 year ago

      Snaps are a standard for apps that Ubuntu’s parent company, Canonical, has been trying to push for years.

      The issue that most people have with them, is that Canonical controls the servers, which are closed source. Meaning that only they can distribute Snap software, which many Linux users feel violates the spirit & intention of the wider free and open source community.

      Appimages and Flatpaks are fully open source standards, anybody can package their software in those ways and distribute them however they want.

      .deb files are software packaged for the Debian distribution, and frequently also work with other distros that are based on Debian, like Linux Mint.

      • Dop@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Thanks, I recently needed picocrypt and not being comfortable with the terminal, snap were a rather convenient way to get it installed, I’ll avoid them from now on.

    • pixelscript@lemm.ee
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 year ago

      The primary thing I hate about them is that every snap package appears to your system as a separate mounted filesystem. So if you look in your file explorer, you can potentially see dozens of phantom drives clogging up your sidebar.

    • merthyr1831@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      Nothing necessarily at the tech level. They’re more capable than Appimages or flatpaks to the point that you can use it to build a reproducible system hardened against tampering or defective updates.

      The downside is that it’s controlled entirely by canonical, has limited abilities (if any?) for hosting storefronts/packages outside of their ecosystem, and said ecosystem is insecure and has already allowed multiple waves of malicious apps to reach end users because of poor moderation of listings masquerading as legitimate versions.

      Canonical has also been increasingly hostile to flatpaks - removing it from Ubuntu and derivatives by default to push users towards snap.

      The whole loopfs thing is just an annoyance, but the aggressive posturing by canonical as well as the closed nature of the storefront that has led to malicious attacks on end users is enough to give it more than a few haters.

    • kalpol@lemm.ee
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      1 year ago

      The snap store is some proprietary store Canonical runs, and snaps are friggin huge in size. I don’t really know though as I don’t use Ubuntu anymore

      • merthyr1831@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Size isn’t an issue imo. Applications are bulky for many more reasons than their packaging formats.

  • aesthelete@lemmy.world
    link
    fedilink
    arrow-up
    10
    ·
    edit-2
    1 year ago

    I hate fucking snap. It might be enough to make me switch distros if Ubuntu keeps up with it (which I am sure they intend to).

    The continual “you have new snaps” or whatever it was message every time I’m just trying to have a web browser open made me eventually figure out how to install firefox for real on all of my computers.

    EDIT: I think you may have convinced me to try out Debian on my next OS installation.

    • Varyag@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      They’ve been doing snaps for a few years already so it already seems like they’re keeping up with this bullshit (in fact they’re putting more and more stuff there) It’s already the reason people stopped recommending Ubuntu to new users and instead go for Mint or Pop!OS