this post was submitted on 05 Jul 2024
743 points (94.0% liked)

linuxmemes

20686 readers
881 users here now

I use Arch btw


Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 12 points 2 months ago (4 children)

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.

[–] [email protected] 11 points 2 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.

[–] [email protected] 8 points 2 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.

[–] [email protected] 3 points 2 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.

[–] [email protected] 1 points 2 months ago* (last edited 2 months ago) (1 children)

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

edit: I can't read

[–] [email protected] 9 points 2 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.