I was looking at this yesterday. I haven’t tried it yet, but I think I’m going to either give it a shot or try something like what fly.io does to launch container images using firecracker.
I've been working on a single bug for nearly 3 weeks. I think my "I'm getting closer to understanding this" is starting to lose credibility with my team.
The one thing missing from the trinity is “effort”. For instance, you could make any Dal, which would fit the trinity, but takes a lot of time. There are books with hundreds of Dal recipes that all taste different and work, too. And this is just one example. Less than a dollar a meal if made in bulk with rice.
You know, thinking back, we should never have trusted that stupid infographic. It was a lie from the get go. It was a food triangle. This is a true pyramid.
Manjaro was my intro to Linux, but now that I know more about it, I can’t recommend it in good conscience. Letting their SSL certs expire is something that happens (even though they could automate it), but telling their users to change their clocks so it works is a big no-no.
Worse than that is how they manage packages from upstream. Simply freezing them for two weeks is, in my opinion, the worst of both worlds. You don’t get timely security updates, but you still end up with the issues of being on the bleeding edge - just late. It also means that if you use the AUR (which is really one of the biggest perks of Arch-based systems), it’s possible that the necessary dependencies are out of date.
I think that if one wants “Arch with an installer” they should go with EndeavourOS, or try the archinstall script.
Sure. When it comes to updates, Manjaro is pretty much doing what every single other distro is doing. Updates that are buggy don’t get pushed to the stable branch until they’re fixed up, and security updates tend to get pushed through faster than feature updates. The time period that updates get held up by is not a fixed duration, it depends on the specific package and update and can be anywhere between a few days and a few weeks.
As a concrete example, with some major Plasma updates Manjaro has waited for three or even four point releases (4 / 8 weeks) before considering it stable enough vs the newest point release of the previous major release, and following point releases after that get pushed to stable much faster.
As another point, even Arch has a very similar process… Their policy on pushing updates is far more geared towards pushing updates quickly than towards not breaking things, but otherwise it’s pretty much the same.
Manjaro packages start their lives in the unstable branch. Once they are a deemed stable, they are moved to the testing branch, where more tests will be realized to ensure the package is ready to be submitted to the stable branch
lemmy.world
Active