Manjaro was more unstable than Arch ever was, for me.
My experience was:
They would mess with Arch packages and muck things up.
It relied on AUR some, which also messed things up.
3rd party repos or AUR didn’t work, as its not in sync with upstream arch.
…Holding back packages didn’t fix anything anyway. It just delayed fixes. I found myself trying to install upstream Arch packages.
It turns out Arch Linux is more tested and “held back” than people give it credit for. There’s little to gain from forking like that, instead of just contributing to upstream arch testing.
Not to mention the cert thing. Manjaro really did let certs expire many times. When I was new to linux, that took me forever to figure out.
I found myself trying to install upstream Arch packages.
You realize that’s how you broke, right? It’s like installing Debian packages on Ubuntu.
It relied on AUR some, which also messed things up.
How does it rely on AUR?
3rd party repos or AUR didn’t work, as its not in sync with upstream arch.
What 3rd party repos?
AUR works perfectly fine… when it works. AUR is a mess of its own. It’s chock full of malware as we speak and it’s not accepted as a reference on Arch or any other Arch-based distro. Saying an Arch distro “doesn’t work with AUR” is completely irrelevant at the best of times.
Not to mention the cert thing. Manjaro really did let certs expire many times. When I was new to linux, that took me forever to figure out.
Did you spend a lot of time reading the webpage, or?.. Because that’s the only cert that expires, the mirros and the forums never did. What exactly were you figuring out?
This was many years ago, when I didnt know much about linux, and yes many lessons were learned. Though I distinctly remember instances where I couldnt update Manjaro packages because of expired certs.
To clarify some points:
On packages/AUR, I was desperate, because upstream Arch had some critical fixes that werent shipped to Manjaro yet. Clearly this didnt work out well.
AUR specifically breaks with Manjaro because AUR targets upstream arch as a base. When a dependant Arch package updates, the AUR package immediately updates to that new dependecy if its being maintained. But since Manjaro delays the upstream updates, this AUR package will break if its updated.
AUR specifically breaks with Manjaro because AUR targets upstream arch as a base. When a dependant Arch package updates, the AUR package immediately updates to that new dependecy if its being maintained. But since Manjaro delays the upstream updates, this AUR package will break if its updated.
Again, using the AUR as the standard for evaluating any Arch-based distro is really not cool.
Leaving that aside, the exact thing you’ve mentioned can happen on vanilla Arch, if the AUR package you are trying to install is based on Arch packages that you haven’t received yet. So you’d have to upgrade your system every time you’re trying to update or install an AUR package to be sure.
since Manjaro delays the upstream updates, this AUR package will break if its updated.
It won’t break, it will either succeed compiling or not with the older packages. If it succeeds, no harm done. If it doesn’t, you still have the previous version.
The unlikely corner case is that the new AUR package version relies on new API/features that only exist in newly released Arch packages and you absolutely must have the latest version right now. But then you’re using the wrong distro for that.
I was desperate, because upstream Arch had some critical fixes that werent shipped to Manjaro yet.
Manjaro ships critical updates out of band, without waiting for regular batch updates.
Manjaro was more unstable than Arch ever was, for me.
My experience was:
They would mess with Arch packages and muck things up.
It relied on AUR some, which also messed things up.
3rd party repos or AUR didn’t work, as its not in sync with upstream arch.
…Holding back packages didn’t fix anything anyway. It just delayed fixes. I found myself trying to install upstream Arch packages.
It turns out Arch Linux is more tested and “held back” than people give it credit for. There’s little to gain from forking like that, instead of just contributing to upstream arch testing.
Not to mention the cert thing. Manjaro really did let certs expire many times. When I was new to linux, that took me forever to figure out.
You realize that’s how you broke, right? It’s like installing Debian packages on Ubuntu.
How does it rely on AUR?
What 3rd party repos?
AUR works perfectly fine… when it works. AUR is a mess of its own. It’s chock full of malware as we speak and it’s not accepted as a reference on Arch or any other Arch-based distro. Saying an Arch distro “doesn’t work with AUR” is completely irrelevant at the best of times.
Did you spend a lot of time reading the webpage, or?.. Because that’s the only cert that expires, the mirros and the forums never did. What exactly were you figuring out?
Whoa nellie.
This was many years ago, when I didnt know much about linux, and yes many lessons were learned. Though I distinctly remember instances where I couldnt update Manjaro packages because of expired certs.
To clarify some points:
On packages/AUR, I was desperate, because upstream Arch had some critical fixes that werent shipped to Manjaro yet. Clearly this didnt work out well.
AUR specifically breaks with Manjaro because AUR targets upstream arch as a base. When a dependant Arch package updates, the AUR package immediately updates to that new dependecy if its being maintained. But since Manjaro delays the upstream updates, this AUR package will break if its updated.
Yes, I know AUR is filled with malware now.
Again, using the AUR as the standard for evaluating any Arch-based distro is really not cool.
Leaving that aside, the exact thing you’ve mentioned can happen on vanilla Arch, if the AUR package you are trying to install is based on Arch packages that you haven’t received yet. So you’d have to upgrade your system every time you’re trying to update or install an AUR package to be sure.
It won’t break, it will either succeed compiling or not with the older packages. If it succeeds, no harm done. If it doesn’t, you still have the previous version.
The unlikely corner case is that the new AUR package version relies on new API/features that only exist in newly released Arch packages and you absolutely must have the latest version right now. But then you’re using the wrong distro for that.
Manjaro ships critical updates out of band, without waiting for regular batch updates.