this post was submitted on 30 Mar 2024
198 points (96.3% liked)
linuxmemes
21197 readers
141 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
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
Is it actually running snap or just unpacking its content and running it as a normal flatpak?
It's unpacking the snap and running the contents.
Neither. The Flatpak is built by unpacking the contents of the snap, after which it's a completely normal Flatpak.
Snaps are just squashfs images with that package and its dependencies, so if the snap isn't doing something fancy like using patchelf or depending on content snaps, it makes a lot of sense that the snap would be extractable and usable for Flatpak. It's probably doable the other way around too, though as far as I know snapcraft doesn't have an official way to use a Flatpak as its source like Flatpak does with snaps.