Linux

62676 readers

251 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 6 years ago

MODERATORS

nooter692@lemmy.ml

AgreeableLandscape@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Systemd-sysext Help Needed (lemmy.world)

submitted 4 days ago by filister@lemmy.world to c/linux@lemmy.ml

15 comments fedilink hide all child comments

I am running Bluefin immutable distro and I would like to test Niri. I found on the net that the cleanest way is to use systemd-sysext and I have managed to install Niri using the community extensions.

Now I would like to install Dank Material Shell, and it has a couple of pre-requisites and I am clueless how I can add them again with systemd-sysext.

I tried to look for additional information, but found very little on the matter. Do any of you have experience with this?

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

[–] j0rge@lemmy.ml 1 points 10 hours ago (1 children)

No they would brew install neovim. System-level package management goes away entirely, that's the point.

What new package managers? homebrew has been around for years. What problems are you describing? If you mean read only root that has been around since the 1980s. The problem as you describe it has been removed, you move on from package based entropy to image based systems.

This isn't a trend, modern linux is this way, it's just the desktop that has been behind until now.

[–] nobody_1677@lemmy.world 1 points 1 hour ago* (last edited 29 minutes ago)

I'm saying that we should be able to use package managers like DNF similarly to homebrew. Rather than managing system packages, it would only be used for packages the user installs. Whether it installs them into /usr/local, /home/dnf, ~/.local/bin doesn't matter. All that matters is that it's not managing system packages or mixing system-installed/user-installed packages.

Homebrew isn't perfect. Awhile ago I tried to go all homebrew for my packages, but sshfs ended up not working (maybe a SELinux issue?). So I had to fallback to overlaying the package. Simiarly, I tried to install tailscale from brew, couldn't get it to work.

It's just that in "immutable" (I know how much you hate the term lol), there's package manager fatigue.

There's flatpak, which is only meant for GUI apps but for certain GUI apps (like IDEs), it's not good.
There's distrobox, which works for both GUI and CLI, but it adds some friction and sometimes the containerization breaks certain functionality.
Brew largely avoids the issues of distrobox and works for GUI and CLI, but the GUI app selection is limited and as I mentioned, sshfs and tailscale didn't work for me there.
And so to work around the issues of those 3, we get yet another way to install packages (systemd system extensions
(and of course that's not even speaking of snap, appimage, cpak, unpackaged apps, etc)

My thesis is essentially that we're creating too many package package managers with too many compromises. Traditional package management is far from perfect, but at least those package managers, you can do essentially anything. Brew could be that, if it had more GUI apps and maybe better SELinux integration (I say that not knowing for 100% sure that SELinux was the cause of my sshfs issuse). I would like for people to take a step back and find simpler solutions, make a single package manager that can handle any kind of package.

Edit: correction, tested again and sshfs is actually working, not sure what was causing the original issue. though I still have sshfs overlayed, maybe that provides some necessary dependency or SELinux tweak?