Linux

48090 readers

729 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

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

The Cloud Native Linux Desktop Model (e.g. Silverblue) (www.youtube.com)

submitted 1 year ago by mrh@mander.xyz to c/linux@lemmy.ml

14 comments fedilink hide all child comments

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

[–] mogoh@lemmy.ml 1 points 1 year ago

I think flatpak could perfectly fine for installing cli applications even though it is designed for desktop applications.

Shoving CLIs into flatpaks could be a thing but that wouldn’t really solve a problem, it would just mean adding one more ocean to boil and someone would have to volunteer to package htop for the 30th time.

Flatpak is distribution independent, which means, it could be actually reduce repackaging.

flatpaks and containers use the same kernel tech underneath, cgroups and namespaces, it’s just a specific implementation designed for desktop apps, and it has things like portals and stuff that’s specific for gui apps.

While that is true, I don't see, why this is a problem for CLI applications to be installed and run via flatpaks.

Direct package management in your home dir - also an option, you can just install homebrew, nix, or tea or whatever install packages in your home directory and then it’s totally decoupled from the system.

Can you explain, why this works better, than flatpaks? I mean it does not matter what flatpaks were intended for originally, if they do the job just fine.

So for example, if you use silverblue, you use htop, but it wouldn’t make sense as a flatpak when there’s a full fedora installation delivered via a container already on your desktop, you’d just dnf install htop and move on.

I found this approach lacking, because:

I always have to remember what is the right container for the right tool.
Installing software can be quite annoying. I can't simply add some dnf install foo in a bashscript. Controlling a container via bash is not that easy (or, I don't know how it works)
Tracking installed software is painful. Now I have to check every container, if and where something is installed.