How? I’ve been using it for 3 years now as my daily driver, it’s one of the most pleasant distros I’ve ever used. I don’t understand how people break it.
It’s probably related to installing packages through the AUR, even though it’s known to be unsupported on Manjaro specifically due to their policy of holding back packages.
I don’t even think it should be avoided at all times. Just approach it through an Arch-container, Distrobox can streamline that process, and everything should be gucci.
I have something like 70 AUR packages installed and it’s very seldom I have problems.
There isn’t any significant difference in AUR compatibility between Manjaro, Arch or any other Arch based distro. I believe this to be an often misunderstood issue.
When you install an AUR package it will work now, on the current state of the distro (current package versions). Later, as you upgrade packages, AUR packages will gradually start failing to work. This is the same on any Arch distro and it depends on how often you upgrade. If anything, by delaying packages by 2 weeks Manjaro will also delay potential incompatibility.
TLDR is that all AUR packages will break eventually and have to be reinstalled periodically, on any distro.
I have something like 70 AUR packages installed and it’s very seldom I have problems.
I’m glad to hear that you’re able to dodge problems more often than not. But even if you wouldn’t have any problems at all, it’s undeniable that the model of Manjaro + AUR is fundamentally broken. No amount of copium, Stockholm-syndrome or masochism would change that.
There isn’t any significant difference in AUR compatibility between Manjaro, Arch or any other Arch based distro. I believe this to be an often misunderstood issue.
Don’t you think that Manjaro’s model of holding back packages conflicts with the AUR that primarily targets Arch which (by design) doesn’t hold back packages? And, if you agree that it conflicts, don’t you think that this actually is a very significant difference as two distinct programs/binaries/software/whatever might rely on two different versions of the same dependency? It’s like a schoolbook example of what dependency hell is*.
When you install an AUR package it will work now, on the current state of the distro (current package versions). Later, as you upgrade packages, AUR packages will gradually start failing to work. This is the same on any Arch distro and it depends on how often you upgrade. If anything, by delaying packages by 2 weeks Manjaro will also delay potential incompatibility.
Fam, with all due respect, I’d like to invite you to educate yourself on this matter. Because, apologies for saying this, there’s just an awful lot of misinformation, conflation and confusion present in this paragraph.
TLDR is that all AUR packages will break eventually and have to be reinstalled periodically, on any distro.
I agree that packages everywhere on all distros may break at some point; that’s just how software is. Though, nothing condones taking on a defeatist stance towards package breakage.
there’s just an awful lot of misinformation, conflation and confusion present in this paragraph.
Then explain what it is. One thing I’ve noticed from most Manjaro detractors is that they can never quite put their finger on exactly what’s wrong with it, they just issue vague statements like these.
Most AUR packages are source so they will link dynamically against whatever is installed on your system, be it Arch or Manjaro. There isn’t much (if any) binary incompatibility between Arch and Manjaro.
The two weeks delay is insignificant. If anything, the delay helps a compiled AUR package remain compatible longer, because the system changes that will break it will come to weeks late.
If there were any significant incompatibility between Arch and Manjaro it would be noticed with AUR binary packages first and foremost. But those packages usually download binaries that were meant to be long-term compatible for the most part and will only break after very long intervals (years) during huge upheavals of the library landscape.
How? I’ve been using it for 3 years now as my daily driver, it’s one of the most pleasant distros I’ve ever used. I don’t understand how people break it.
It’s probably related to installing packages through the AUR, even though it’s known to be unsupported on Manjaro specifically due to their policy of holding back packages.
This
I ran Manjaro for years. I think I ever needed, wanted something out of aur once for a simple something.
I don’t even think it should be avoided at all times. Just approach it through an Arch-container, Distrobox can streamline that process, and everything should be gucci.
I have something like 70 AUR packages installed and it’s very seldom I have problems.
There isn’t any significant difference in AUR compatibility between Manjaro, Arch or any other Arch based distro. I believe this to be an often misunderstood issue.
When you install an AUR package it will work now, on the current state of the distro (current package versions). Later, as you upgrade packages, AUR packages will gradually start failing to work. This is the same on any Arch distro and it depends on how often you upgrade. If anything, by delaying packages by 2 weeks Manjaro will also delay potential incompatibility.
TLDR is that all AUR packages will break eventually and have to be reinstalled periodically, on any distro.
I’m glad to hear that you’re able to dodge problems more often than not. But even if you wouldn’t have any problems at all, it’s undeniable that the model of Manjaro + AUR is fundamentally broken. No amount of copium, Stockholm-syndrome or masochism would change that.
Don’t you think that Manjaro’s model of holding back packages conflicts with the AUR that primarily targets Arch which (by design) doesn’t hold back packages? And, if you agree that it conflicts, don’t you think that this actually is a very significant difference as two distinct programs/binaries/software/whatever might rely on two different versions of the same dependency? It’s like a schoolbook example of what dependency hell is*.
Fam, with all due respect, I’d like to invite you to educate yourself on this matter. Because, apologies for saying this, there’s just an awful lot of misinformation, conflation and confusion present in this paragraph.
I agree that packages everywhere on all distros may break at some point; that’s just how software is. Though, nothing condones taking on a defeatist stance towards package breakage.
Then explain what it is. One thing I’ve noticed from most Manjaro detractors is that they can never quite put their finger on exactly what’s wrong with it, they just issue vague statements like these.
Most AUR packages are source so they will link dynamically against whatever is installed on your system, be it Arch or Manjaro. There isn’t much (if any) binary incompatibility between Arch and Manjaro.
The two weeks delay is insignificant. If anything, the delay helps a compiled AUR package remain compatible longer, because the system changes that will break it will come to weeks late.
If there were any significant incompatibility between Arch and Manjaro it would be noticed with AUR binary packages first and foremost. But those packages usually download binaries that were meant to be long-term compatible for the most part and will only break after very long intervals (years) during huge upheavals of the library landscape.
For example, it was grub issue that prevented me to boot after system update. No AUR was involved.
My Arch Linux devices were not affected.
Just a single example. I don’t recall what was the issue previous 2 times…