Some of the code written for Pkgcore has been pulled back into Portage, such as the cache-handling code.Its 0.3 release finally reached a point of usability because it added frontends with comprehensible output—one that mirrors Portage and another that mirrors Paludis.

etc portage package use 39 needs updating-20etc portage package use 39 needs updating-88

Together, these two developments motivated creation of an Ebuild API or EAPI.

The current generation will be EAPI=0, which is being documented in a formal specification.

Today, it's extremely difficult to add features to Portage or interface with it because there are complex interdependencies and a pretty much nonexistent API.

Consequently, two groups of developers decided to start fresh with two separate projects: paludis and pkgcore.

And of course, one benefit over Paludis is that you don't need to use the occasionally less-than-speedy g to compile it.

Pkgcore and Paludis seem fairly well-matched in the features department.Posted Jul 5, 2007 UTC (Thu) by smitty_one_each (subscriber, #28989) [Link] Great article.Venerable though portage may be, the nail in its coffin is going to be benchmarking.They both support sets, the additional dependency flexibility, integrated checking for security vulnerabilities, and Portage's on-disk format.Another useful feature they both support is the ability to restrict packages to install based on their licenses.Furthermore, Paludis added a number of features Gentoo developers have been requesting for years that add flexibility to how dependencies can be specified.