Thread #108678199
HomeIndexCatalogAll ThreadsNew ThreadReply
H
File: file.png (1.4 MB)
1.4 MB
1.4 MB PNG
Is moving towards a single cross-distro package manager the necessity to make linux sustainable for the general population?
+Showing all 17 replies.
>>
Yes, but its also a bad idea. When I first started using Linux I didnt understand wtf package managers were in the first place.
>>
>>108678199
just use Homebrew, it works on Linuk and macOS
>>
non-issue
the general population just needs a frontend that doesn't suck cock and/or download buttons on the program's website like windows
guess what, the trillions of Debian-based distros have had that since forever
doesn't seem like it worked
>>
>>108678199
Yes, but not a goal by itself.
Having unified package manger doesn't matter. Having unified packages does. Linux is shit because of the opportnity cost of package maintenance leaves nothing for actually making it better
>>
>>108678199
Just use pkgsrc
>>
>>108678199
xkdc bait thread
>>
>>108678199
Yes and it's already happening with nix
Even Fedora comes with nix now
>>
>>108678244
Except homebrew sucks ass. Slow AF. I don’t want to update my whole system every time I install a package, and I don’t want to have to fiddle with my system every time because some dependency was installed without homebrew and now nothing works. Give me pacman/paru and be done with it.
>>
>>108678302
It didn't work because Debian didn't integrate it properly. You can't just download a .deb file and install it, you have to install gdebi, and when you open a .deb with gdebi it usually doesn't work because it needs sudo perms and you can't elevate to sudo within gdebi because it's a piece of shit, so you need to su into a terminal, navigate to the downloads folder and run "sudo gdebi <program_name>". And then it still might fail for unknown reasons, maybe a glibc incompatibility.
>>
pacman and portage are the only viable solutions
>>
we don't want a new npm
>>
>>108678199
Here's a mind blower for ya: they're all cross distro
>>
Source code that is portable and has sane build constraints is the only true way. Anything else is a weak compromise to compensate for poor engineering.
>>
we already have one, it's called flatpak
>>
>>108678199
No, most people probably don't care as long as it shows up in the software store/center.

But for developers it's necessary. Especially for proprietary stuff where at best you might get a broken RPM along with the officially supported Ubuntu package. That said first we need a decent alternative, Snap is Ubuntu cancer, Flatpak barely works on a good day, and Appimage is mostly dead.
>>
>>108678199
should be packagectl part of systemd.
>>
>>108678199
No, we need to ship everything as an AppImage. Package managers where a mistake and should only be used for core system components (kernel, daemons, base desktop environment etc)

Reply to Thread #108678199


Supported: JPG, PNG, GIF, WebP, WebM, MP4, MP3 (max 4MB)