- cross-posted to:
- lemmyshitpost@lemmy.world
- cross-posted to:
- lemmyshitpost@lemmy.world
PSA: DO NOT INSTALL xx.04 releases!!!
- The .04 stands for “April”, commonly known for “April Fools”.
- Many projects use the term “LTS”, meaning “Lies, Tricks, and Slander”. So called ‘Enterprise’ users often promote these releases to “own the noobs”. Be warned!
Or just use Debian, if you really enjoy the sluggishness and shitty dependency management of APT.
Alternatively you could switch to Arch and the glory that is pacman (or, even better, yay).
…But that’s none of my business.
For a main desktop, absolutely.
For low maintenance servers and vms? Staying with Debian.
For a laptop on which Arch gives issues (mine where with battery when standby). POP-OS has been working well.
The server software world is debian based. Fortunately/unfortunately.
Horses for courses, desktop and server OS’s should have different priorities and approaches.
Paru is a rust rewrite(ish) of yay and therefor even even betterer
Edit: uncorrecting autocorrect
File based package review and automatic git tracking + merge of local PKGBUILD changes are pretty attractive features. I’ll give it a try.
No, thanks. I like my distro not to break with updates ever. Arch breaks stuff every few months at least. I know cause I have used it. Also I prefer to just have fewer updates in general.
There are 2 wolves inside you.
One uses the yay and can install anything from AUR.
The other can install propreitery .deb packages your university vpn comes in to submit homeworks.There is a crow pulling both wolves by the tail called “bedrock linux” that can install packages using both apt and aur.
The crow is the most dangerous.
There is a crow pulling both wolves by the tail called “bedrock linux” that can install packages using both apt and aur.
Oh god… what happens when they both try to pull the same library as a dependency, but slightly different versions because different repos?
apt’s dependency management is shit?
let me see if I understood this straight, someone replaced a core library which caused apt to rightfully to belive the package is not there which caused all packages that depend on it to be marked for autoremoval as expected





