From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1FgMi9-00085Y-18 for garchives@archives.gentoo.org; Wed, 17 May 2006 14:09:13 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.6/8.13.6) with SMTP id k4HE5oNF006769; Wed, 17 May 2006 14:05:50 GMT Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by robin.gentoo.org (8.13.6/8.13.6) with ESMTP id k4HDvRtO023077 for ; Wed, 17 May 2006 13:57:27 GMT Received: from [172.23.170.145] (helo=anti-virus03-08) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1FgMWl-0004TQ-10 for gentoo-dev@lists.gentoo.org; Wed, 17 May 2006 14:57:27 +0100 Received: from [213.121.151.206] (helo=snowdrop.home) by asmtp-out1.blueyonder.co.uk with esmtpa (Exim 4.52) id 1FgMWk-0005rQ-F7 for gentoo-dev@lists.gentoo.org; Wed, 17 May 2006 14:57:26 +0100 Date: Wed, 17 May 2006 14:57:05 +0100 From: Ciaran McCreesh To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Paludis and Profiles Message-ID: <20060517145705.70b1f15a@snowdrop.home> In-Reply-To: <200605171204.33647.pauldv@gentoo.org> References: <20060516161549.442b4d8a@localhost> <20060517000910.5e1f1ccb@sven.genone.homeip.net> <200605170115.33956.kugelfang@gentoo.org> <200605171204.33647.pauldv@gentoo.org> X-Mailer: Sylpheed-Claws 2.1.1 (GTK+ 2.8.17; i686-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: 5ad6b7e9-8cb3-4bb2-b941-dbd50f59fc1f X-Archives-Hash: de8f3baa84bbefaafc9c0bd77b7c5eb6 On Wed, 17 May 2006 12:04:33 +0200 Paul de Vrieze 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