this post was submitted on 16 Sep 2024
845 points (97.5% liked)

linuxmemes

21611 readers
1508 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 2 years ago
    MODERATORS
    845
    Snap out of it (lemmy.zip)
    submitted 3 months ago* (last edited 3 months ago) by 299792458ms@lemmy.zip to c/linuxmemes@lemmy.world
     

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

    you are viewing a single comment's thread
    view the rest of the comments
    [–] BigDanishGuy@sh.itjust.works 55 points 3 months ago* (last edited 3 months ago) (3 children)

    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 12 points 3 months 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 3 points 3 months ago* (last edited 3 months ago) (1 children)

    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.

    [–] Omniraptor@lemm.ee 2 points 3 months ago

    in the end we end up using containers afaict