741
submitted 4 months ago by renzev@lemmy.world to c/linuxmemes@lemmy.world
you are viewing a single comment's thread
view the rest of the comments
[-] F04118F@feddit.nl 12 points 4 months ago

Is compiling it yourself with the time and effort that it costs worth more than a few GB of disk space?

Then your disk is very expensive and your labor very cheap.

[-] cley_faye@lemmy.world 11 points 4 months ago

For a lot of project "compiling yourself", while obviously more involved than running some magic install command, is really not that tedious. Good projects have decent documentation in that regard and usually streamline everything down to a few things to configure and be done with it.

What's aggravating is projects that explicitly go out of their way to make building them difficult, removing existing documentation and helper tools and replacing them with "use whatever we decided to use". I hate these.

[-] BeigeAgenda@lemmy.ca 8 points 4 months ago

I should have noted that I'll compile myself when we are talking about something that should run as a service on a server.

[-] recarsion@discuss.tchncs.de 3 points 4 months ago

99% of the time it's just "make && sudo make install" or something like that. Anything bigger or more complicated typically has a native package anyway.

[-] ReveredOxygen@sh.itjust.works 1 points 4 months ago* (last edited 4 months ago)

They didn't say anything about compiling it themselves, just that they prefer native packages to flatpak

edit: I can't read

[-] Batbro@sh.itjust.works 9 points 4 months ago

2 comments up they said

If the choice then is flatpack vs compile your own, I think I'll generally compile it, but it depends on the circumstances.

this post was submitted on 05 Jul 2024
741 points (93.7% liked)

linuxmemes

21281 readers
488 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