this post was submitted on 25 Sep 2023
1150 points (92.3% liked)

linuxmemes

21393 readers
1580 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 1 year ago
    MODERATORS
    [email protected]
    [email protected]
    [email protected]
    1150
    Superiority brings controversy (aprogrammerlife.com)
    submitted 1 year ago by [email protected] to c/[email protected]
    315 comments fedilink hide all child comments
     

    Re-creation of someone else's post because the original was removed and I found it funny when I first saw it

    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 10 points 1 year ago (1 children)

    All potentially fantastic ideas had the original author bothered to package in any of those formats. Much more common is the only release is a .deb built for an ancient version of Ubuntu, leading to my above frustrstions.

    [–] [email protected] 3 points 1 year ago* (last edited 1 year ago) (1 children)
    1. Stop bothering with dead software.
    2. You can repackage old FOSS source code into any of those containers and install and use it that way. Nothing is stopping you, the tools are free and widely documented. You don't need to own the FOSS repository to repackage it, and actually a huge chunk of containers are packaged by people not affiliated with the development project of the software.
    [–] [email protected] 1 points 1 year ago

    I think we will become better served over time by using systems like the AUR or nix as it seems quite straightforward to make new software available with them. Both of those systems define the method a package should be built with, so even if the maintainer is long gone and the package hasn't been updated in a long time it will probably still be possible to build, or any changes needed to build it can be easily shared to save other people troubleshooting effort.

    The drawbacks are: nix doesn't seem to have an elegant way to define that users or groups should be created (e.g. at least one package providing locate requires that) (though it does have at least one non-elegant way and one manual but less non-elegant way), and a package usable with pacman has lacked a definition of what version of every dependency it requires in at least one case where it would have been useful to me (even though that is possible apparently), so if anything made a backwards-incompatible change you may not be able to use the package manager alone to troubleshoot.