this post was submitted on 02 Oct 2023
385 points (93.8% liked)

linuxmemes

26331 readers
15 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 users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • 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.
    • 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, no politics, no trolling or ragebaiting.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    • Β 

    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 remove France.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    385
    And Gentoo as well, but shush (lemmy.dbzer0.com)
    submitted 2 years ago* (last edited 2 years ago) by SimplyTadpole@lemmy.dbzer0.com to c/linuxmemes@lemmy.world
    102 comments fedilink hide all child comments
     

    you are viewing a single comment's thread
    view the rest of the comments
    [–] frippa@lemmy.ml 12 points 2 years ago (3 children)

    I'm a noob, isn't every (open source) program aviable for every distribution if you compile it from source? It's all Linux in the end (i never compiled a program from source, so I don't know if it's easy at all)

    [–] deadcade@lemmy.deadca.de 6 points 2 years ago

    Some programs may use libraries or tools specific to a distributions package manager. For example, yay, an AUR helper/pacman wrapper. You would have a very hard time getting it to work on Debian.

    Other programs might only include build scripts for a distro specific build system. For example, a program might skip using a Makefile, and do everything in the Arch-specific PKGBUILD.

    Generally though, most software uses a standard cross-distro (or even OS) build system. In this case, compiling from source would be an option on any distro. The program might still only be packaged for Arch/NixOS/Gentoo (or others), as it is a very simple process to do so.

    [–] thelastknowngod@lemm.ee 3 points 2 years ago (1 children)

    Usually the only tricky part of compiling from source is tracking down dependencies. The package manager does that for you normally but you're not using the package manager when compiling from scratch. The actual building (even compiling a kernel) isn't all that complicated.

    [–] uis@lemmy.world 2 points 2 years ago (1 children)

    Usually developers list dependencies in README anyway

    [–] thelastknowngod@lemm.ee 1 points 2 years ago (1 children)

    True. It's the dependencies of dependencies where the tricky part starts.

    [–] uis@lemmy.world 2 points 2 years ago (1 children)

    Dependencies almost always are present in distro repos. What's tricky?

    [–] thelastknowngod@lemm.ee 2 points 2 years ago (1 children)

    If you need the python header files, depending on your distro, you may need to install python3-dev, python3-devel, python3, or some other variation on the name. For a novice, this might not always be obvious and they might not know things like apt-file are helpful for figuring it out.

    [–] uis@lemmy.world 1 points 2 years ago* (last edited 2 years ago) (1 children)

    Huh. Shouldn't apt install header dependencies too? I'm using system where every package comes with headers, so I don't install headers separately.

    [–] thelastknowngod@lemm.ee 1 points 2 years ago

    Debian and RedHat based distros typically do not bundle them together. The have separate -dev and -devel packages for headers.

    [–] SomeBoyo@feddit.de 1 points 2 years ago

    Yes, but not every package is in every repository