On Wed, 17 May 2006 12:04:33 +0200 Paul de Vrieze <[EMAIL PROTECTED]> wrote: | - Paludis must be able to handle a standard portage /var/db/pkg tree. | This means that paludis can read it, and write it. Enabling mixing | portage and paludis up to some degree.
Paludis can read a Portage-generated VDB. Portage can't read a Paludis-generated VDB, because Paludis has more features. | - Paludis must work with all current ebuilds, Portage does not work with all current ebuilds. | and support all features of portage. That's insane. Why should we support Portage-style 'candy' spinners? | This includes recognition of EAPI Funnily enough, unlike Portage, Paludis has full EAPI handling. | and no renaming of the variables used. Why should Paludis emulate Portage internals that no-one uses? | - No part of the tree, except those that by nature are paludis | specific, may require the usage of paludis instead of portage. This | requirement can only be removed after a decision is made by the | council to retire portage in favour of paludis. Again, insane. EAPI allows ebuilds using things that developers have been after for years (you know, slot and use deps) to be in the tree in such a way that they appear masked to Portage. That's a large part of the point of EAPI. | - It would be greatly beneficial if paludis would create and use .tbz2 | packages, but this is not essential. Paludis will use its own binary format. -- Ciaran McCreesh Mail : ciaran dot mccreesh at blueyonder.co.uk -- gentoo-dev@gentoo.org mailing list
