741
submitted 3 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
[-] BeigeAgenda@lemmy.ca 38 points 3 months ago

If I can choose between flatpack and distro package, distro wins hands down.

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

[-] ryannathans@aussie.zone 16 points 3 months ago
[-] BeigeAgenda@lemmy.ca 15 points 3 months ago

Because it's easier to use the version that's in the distro, and why do I need an extra set of libraries filling up my disk.

I see flatpack as a last resort, where I trade disk space for convenience, because you end up with a whole OS worth of flatpack dependencies (10+ GB) on your disk after a few upgrade cycles.

[-] F04118F@feddit.nl 12 points 3 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 3 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 3 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 3 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 3 months ago* (last edited 3 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 3 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.

[-] TimeSquirrel@kbin.melroy.org 2 points 3 months ago* (last edited 3 months ago)

I mean it's 2024. I regularly download archives that are several tens or even over 100 GB and then completely forget they're sitting on my drive, because I don't notice it when the drive is 4TB. Last time I cared about 10GB here and there was in the late-2000s.

[-] BeigeAgenda@lemmy.ca 9 points 3 months ago

Great that you have 4tb on your root partition then by all means use flatpack.

I have 256Gb on my laptop, as I recall I provisioned about 40-50gigs to root.

[-] TimeSquirrel@kbin.melroy.org 2 points 3 months ago* (last edited 3 months ago)

I'm sorry. I didn't realize people were still regularly using such constrained systems. Honest. I've homebuilt my PCs for the last 15 years.

[-] tgxn@lemmy.tgxn.net 2 points 3 months ago
[-] uranibaba@lemmy.world -5 points 3 months ago

Why not upgrade your hdd?

[-] Vilian@lemmy.ca 0 points 3 months ago
[-] BeigeAgenda@lemmy.ca 3 points 3 months ago

Yep that's all well and good, but what flatpack doesn't do automatically is clean up unused libs/dependencies, over time you end up with several versions of the same libs. When the apps are upgraded they get the latest version of their dependency and leave the old behind.

[-] 4am@lemm.ee 11 points 3 months ago
[-] fossphi@lemm.ee -1 points 3 months ago
[-] dis_honestfamiliar@lemmy.world 5 points 3 months ago

I'm 100% on this camp.

[-] azenyr@lemmy.world 2 points 3 months ago

I change my opinion depending on which app it is. I use KDE, so any KDE app will be installed natively for sure for perfect integration. Stuff like grub costumizer etc all native. Steam, Lutris, GIMP, Discord, chrome, firefox, telegram? Flatpak, all of those. They don't need perfect integration and I prefer the stability, easy upgrades and ease of uninstall of flatpak. Native is used when OS integration is a must. Flatpak for everything else. Especially since sometimes the distro's package is months/years old... prefering distro packages for everything should be a thing of the past.

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

linuxmemes

21138 readers
589 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!

    founded 1 year ago
    MODERATORS