Equo & Spritz
Yeah, the first one, will be our future binary packages manager, like apt is for debian and yum is for RedHat/FC. It just takes the best from these worlds and the best from Gentoo bringing you to a revolutionary experience. Well, it’s starting to do some real stuff. Like, syncing the repository, do searches inside the repository and local database, download packages, installing them, syncing with Gentoo /var/db/pkg directory and so on. There are still a lot of missing things but you know, when you build a building, the hardest part are the foundations. We have it, and they start to work really well. So, I think that we’re perfectly on track.
Have a look at this screenshot, I was trying to install Fluxbox on a Core Install, pulling in all the missing packages.
So, what’s Spritz then? Easy one. Take YumEx and get it working on Sabayon with Entropy.
Well, to sum up, we’ll have a binary package manager perfectly compatible with Gentoo (it’s up to you) that uses gentoo naming conventions and will let you install our optimized openoffice package (not -bin) in just few seconds. Can you realize it?
Again great idea! I hold thumbs too this project.
This looks very cool. I like choice. One of the things that eventually turned me off about Gentoo was a lack of coice. They wanted to cram long text mode installs down my throat that invariably had problems that had to be googled and solved at great length. With Sabayon i can usually just install and go. Some days a text mode type install is good, other days a quick graphical with quick package install options are *The Only Way to Fly*
On my next pay day I will donate to Sabayon for sure! Keep up the awesome work!
what about USE flags, how are they handled by sabayon prebuilt packages? Are the packages built on default USE flags? is it possible to have more than one binary package of an application, each built with different USE flags and then equo choose according to make.conf the right binary. that would be very nice because it provides the great flexibiliy of gentoo build system with the advantage of binary packages.
To have these binary packages everyone (or at least some trusted people) could upload their packages (which were built by portage) with the infos of make.conf attached.