Its even worse when you force Firefox to use wayland its icon doesn’t even show.

Edit: Oh since everyone now is confused; I only have the flatpak version of Firefox installed yet it doesn’t use the pinned icon and doesn’t even use the firefox icon under wayland at all.

You are viewing a single thread.
View all comments View context
13 points

Yes. I do have some applications installed as flatpak. What’s the problem?

permalink
report
parent
reply
-21 points

That’s the whole problem, don’t use flatpak. It’s the worst way of solving a problem that’s already solved.

permalink
report
parent
reply
13 points
*
  • What problem?
  • How is it already solved?

This comment chain feels like talking to a brick wall. It’s just “don’t use flatpak” over and over again but with different words.

permalink
report
parent
reply
-1 points

The problem with dependencies, that’s the only reason for people to look at flatpak.

See my other comment, and see https://flatkill.org/

permalink
report
parent
reply
9 points

I just feel like you could have provided alternatives? How is it solved? Genuine question…

permalink
report
parent
reply
1 point

Package managers like apt or rpmn(or whatever for your distro) are the standard way to install software. If there’s a good reason to avoid them, OK, but no good reason was stated here.

permalink
report
parent
reply
-1 points

Basically you install the application inside a little OS with dependencies each time you install a flatpak, that OS is rarely updated with security patches and most of the time has full access to the host OS. https://flatkill.org/

This is a lazy and insecure way of distributing applications with no real benefits.

permalink
report
parent
reply
-1 points
*

@lambda @BeigeAgenda

Imo a better alternative to flatpak is the nix package manager, but as I said to the other guy this’ll most likely end up a VHS/betamax situation.

Both things are trying to solve dependency hell in different ways. Flatpak just builds and runs everything in a container, where as nix sets up virtual environments and builds things in isolation with per package dependency trees in an effort to make builds entirely reproducible (to the point that no matter what system you compile on, you will get the same hash).

Edit: as the other guy said, just use your systems package manager unless it doesn’t exist in the repo and you can’t be bothered to package it yourself. It’s the standard recommended method.

permalink
report
parent
reply

linuxmemes

!linuxmemes@lemmy.world

Create post

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!

Community stats

  • 8K

    Monthly active users

  • 1.3K

    Posts

  • 69K

    Comments