Linux

48323 readers

648 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

what are the pros and cons of apt vs flatpak? (lemmy.ml)

submitted 5 months ago by [email protected] to c/[email protected]

73 comments fedilink hide all child comments

target OS is debian or linux mint

you are viewing a single comment's thread
view the rest of the comments

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

That's strange

Seems you can use all the libraries too as if they were binaries. Updated my Fedora post.

Currently testing how to run the freedesktop.org runtime with home permission, this would allow to not give any app permanent home permission.

But wait, you can run apps with different permissions temporarily, right?

Like flatpak run --filesystem=home org.app.name

but I read the PKGBUILDs and understand them.

That is the best way but not scalable for most users. You need access control and trust. On COPR I add the repo of an individual and only get packages from them.

And programs can bypass it anyway with /home/$USER if they're feeling vindictive, though I haven't run into any yet. It'd definitely be nice to have more complete isolation one day.

This is not about isolation, even though this should totally be done. Its just about preventing dotfile mess.

Scalable, you know. A system should stay vanilla in 20 years, in 40 years.

In the end it would be

core minimal system
/etc has some settings pinned or none at all, the rest is always flushed from /usr/etc (issue)
the immutable rest is always upstream
the bootloader is updated with bootupd
flatpaks have their configs isolated, when they are uninstalled, their data is removed
distroboxes are ephemeral, they are used for tasks, managed through a GUI app with a set of commands (like "add this repo" and packages to install, or even building blocks or checkboxes), they are recreated with OS releases
the distroboxes have their own dotfiles which never overlap
the desktop has figured out a way to cleanup old dotfiles

I mean we are not there yet, but close.

I really hate apt.

Apt is an ugly mess and nala might be python bloat but it looks fancy and automates things. Now that it runs on Debian 12 I installed it everywhere.

I really have no idea what to expect. But if I never need to use rpm for querying or whatever again I'll be happy.

Yeah or add curl instructions to projects like librewolf, to avoid needing "oh and on atomic distros you dont use 'dnf blabla' but download it directly".

Even though I like my COPR command...