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.43) id 1E8kMI-0004O6-Rp for garchives@archives.gentoo.org; Fri, 26 Aug 2005 19:59:27 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j7QJvJ0v024086; Fri, 26 Aug 2005 19:57:19 GMT Received: from www.opersys.com (opersys.com [64.40.108.71]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j7QJtZIJ019734 for ; Fri, 26 Aug 2005 19:55:35 GMT Received: from [10.10.10.4] (dsl-135-104.aei.ca [66.36.135.104]) by www.opersys.com (8.9.3/8.9.3) with ESMTP id NAA28736 for ; Fri, 26 Aug 2005 13:31:25 -0700 Subject: [gentoo-dev] [RFC] EAPI From: Kristian Benoit To: gentoo-dev@lists.gentoo.org Content-Type: text/plain Date: Fri, 26 Aug 2005 15:49:35 -0400 Message-Id: <1125085775.16733.55.camel@localhost> 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 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 7bit X-Archives-Salt: d210c50c-250a-45ca-ad88-46cf674ef4f2 X-Archives-Hash: 63290da50938558b7d49cd3e59b5b874 On the EAPI subject Brian just brought back, I had this idea that we could use the same approch XML took with HTML. The ebuild could define which EAPI to use, but instead beiing a version, the EAPI would be an ebuild API definition. The equivalent to the XML's dtd. The ebuild could point to a directory named $PORTDIR/eapi// which would contain a python script named .py. If not already loaded, that plugable eapi would be loaded before processing the ebuild. That way, there is no outdated ebuild format. There is just a default format which is the actual format. It could also be an XML defining the ebuild's build sequence and other particularities a group of ebuild could have. Kristian -- gentoo-dev@gentoo.org mailing list