From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MC1CY-0002ez-22 for garchives@archives.gentoo.org; Thu, 04 Jun 2009 00:53:02 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AAEB6E0102; Thu, 4 Jun 2009 00:53:00 +0000 (UTC) Received: from mail-gx0-f224.google.com (mail-gx0-f224.google.com [209.85.217.224]) by pigeon.gentoo.org (Postfix) with ESMTP id 8A0A0E0102 for ; Thu, 4 Jun 2009 00:53:00 +0000 (UTC) Received: by gxk24 with SMTP id 24so1598056gxk.10 for ; Wed, 03 Jun 2009 17:53:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=gAACTcUlj0Ik59BqoZg5LWTJdbt1lJDV/PfS3pQJVCE=; b=FDtB4N422EwhJQIb8m76Hw77MHpGYsiEkNM0GdbTF8RWA/RLvuEzJVDX3lrd+Wwj8i CBWv5B1NKCzlf80M5MoboudZz6vb3U9AhlweHRs5mmIVPv+rN9RIdIjeOdk53j2ssoEq Bu2951goo0BgrmN0A+JZKPzNJVvE9PXv4r3Ho= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=hPUe1hHJqSo5stH1hcyUV7HrpV3W5rwX9MfXfIG9/teXF1whjuSL5hPYvw4KwW5hpY Y8CD5XuRrmYUnXPSw9iAgwtZcMHJLZ3Rkx3uLVybWc3hfoBmZCr5JaW2Z5gnsaCRaqGs Emtr3q2UjCXgyv/+gQZSTZfmyYHHO3F+i9I6k= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Received: by 10.151.85.11 with SMTP id n11mr1602172ybl.88.1244076780141; Wed, 03 Jun 2009 17:53:00 -0700 (PDT) In-Reply-To: <4A230007.9090708@gentoo.org> References: <200905311556.19190.patrick@gentoo.org> <4A230007.9090708@gentoo.org> From: Wyatt Epp Date: Wed, 3 Jun 2009 20:52:40 -0400 Message-ID: Subject: Re: [gentoo-dev] A new glep: Ebuild format and metadata handling To: gentoo-dev@lists.gentoo.org Content-Type: multipart/alternative; boundary=000e0cd5d02c8dbf86046b7b32f2 X-Archives-Salt: e37daef0-212f-4d7e-9bd4-7ccc33c7a130 X-Archives-Hash: ed0fc1262476d89b74a577e5385ce797 --000e0cd5d02c8dbf86046b7b32f2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On Sun, May 31, 2009 at 6:09 PM, Richard Freeman wrote: > > glep55: See GLEP55. To summarize: The eapi is put into the file name so > that the package manager knows the EAPI (and thus how to handle this file > format). While it simplifies the eapi discovery this comes at a high price > as there is no reliable way to find and validate all ebuilds. It also > enforces some minor limitations, for example EAPI needs to be unique and > cannot be overridden by eclasses. Some people also see it as bad design as > it exposes file internals in the filename. Okay, this has been bothering me....sorry if this is a sort of silly question, but why not just use the (already extant) metadata.xml for the...err, metadata about a package? In any case, I'm strongly opposed to the idea of encoding any more metadata into the filename than is strictly necessary to uniquely identify the file. As both a software developer and a user, please do not do this. Regards, Wyatt --000e0cd5d02c8dbf86046b7b32f2 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Sun, May 31, 2009 at 6:09 PM, Richard Freeman= <rich0@gentoo.org= > wrote:

glep55: See GLEP55. To summarize: The eapi is put into the file name so tha= t the package manager knows the EAPI (and thus how to handle this file form= at). While it simplifies the eapi discovery this comes at a high price as t= here is no reliable way to find and validate all ebuilds. =C2=A0It also enf= orces some minor limitations, for example EAPI needs to be unique and canno= t be overridden by eclasses. Some people also see it as bad design as it ex= poses file internals in the filename.

Okay, this has been bothering me....sorry if this is a sort of sil= ly question, but why not just use the (already extant) metadata.xml for the= ...err, metadata about a package?=C2=A0

In any case, I&= #39;m strongly opposed to the idea of encoding any more metadata into the f= ilename than is strictly necessary to uniquely identify the file.=C2=A0 As = both a software developer and a user, please do not do this.

Regards,
Wyatt
--000e0cd5d02c8dbf86046b7b32f2--