Hello everyone, tonight I uploaded two packages to our unstable branch: one new and one old; one that was already present in our repositories changed its name and the new one took its name. It’s a play on words but allow me to explain: the new package is penguins-eggs-legacy which is nothing other than the old penguins-eggs while the new one is actually penguins-eggs. New because it was completely rewritten from scratch using GO and a minimal part of C.
The only notes I would like to underline is that the packages can coexist in the system, they do not interfere with each other so if someone who has installed penguins-eggs and wants to continue using the old approach will have to install penguins-eggs-legacy and launch eggs-legacy as an executable from the terminal.
From the developer Piero Proietti:
After years of passionate work on penguins-eggs, I am now undertaking its next evolution: the old good penguins-eggs became penguins-eggs-legacy and we have penguins-eggs. The new penguins-eggs is built on oa, a high-performance C-native remastering engine and coa, its intelligent Go orchestrator. This new architecture replaces fragile bash scripts with native Linux kernel syscalls and strict zero-copy principles — delivering a significant leap in speed and reliability. The goal is ambitious: a truly universal approach to Linux remastering. Every distribution is different, yet they all share common roots. oa-tools already supports Alpine, Arch, Debian, Fedora, Manjaro and openSUSE — and aims to prove that a single, unified engine can handle them all.
If anyone would like to learn more you can read here
Have fun easily creating Manjaro rounds but also be prepared for trouble if you deploy them
Do you mean if you decide to release your own custom ISOs using this remastering tool?
Basically, anything you’ve added beyond the standard content of our ISOs. I’m not against these tools – in fact, I helped make it compatible with Manjaro – but to be honest, I wouldn’t be too keen on ISOs created with tools of this kind being distributed on a large scale. As long as it’s done amongst friends, or if the person installing it trusts the person who created it, there’s no problem. But not having access to everything included in the custom ISO could (at least for me) be a cause for concern, as I might include configuration files or binary modifications that can’t be verified. I hope I’ve made myself clear.
