From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Lcz0b-0000oG-Db for garchives@archives.gentoo.org; Fri, 27 Feb 2009 09:27:53 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 950B4E04A1; Fri, 27 Feb 2009 09:27:51 +0000 (UTC) Received: from mail-qy0-f23.google.com (mail-qy0-f23.google.com [209.85.221.23]) by pigeon.gentoo.org (Postfix) with ESMTP id 69CF4E04A1 for ; Fri, 27 Feb 2009 09:27:51 +0000 (UTC) Received: by qyk31 with SMTP id 31so107011qyk.32 for ; Fri, 27 Feb 2009 01:27:51 -0800 (PST) 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 :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=84VOinVLYQnP9q3ZrPWK+Eqesbm8K2BreQw3EEliYtg=; b=hVf9td2TQM96r8OAGF9aDkcBXRuGbvZT+E1qSs92by/5kpHmtOHAZ2UfCT6YE9k2BF XKeB9LPwIAjElrz9lr3SLER20uP4gmyjhHxSSxVdWfF5qKuYec7TfK4zt2JoG/WVolxQ ZQLNphHv9Dlhips1fxI/fM+xcN2PybPVZtkow= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=YCaHr1iChp0gTmxGUz6yveK5acmwbBn9XVm1J+P0q9rEZYanW1HNDbB5cfYa2J3AZc 7YVOAbrSQLUNKCKbHQvbfpbvUPPIRCuh0ByRfExUzretWwUl1myDs2KmW5LhZ8C6KuKM m3T0xsvYaBGe4wI8M9UBUWGhhsq4YoYodyupE= 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.229.99.211 with SMTP id v19mr1715300qcn.97.1235726871111; Fri, 27 Feb 2009 01:27:51 -0800 (PST) In-Reply-To: <49A472E3.1010204@gentoo.org> References: <49A472E3.1010204@gentoo.org> Date: Fri, 27 Feb 2009 04:27:50 -0500 Message-ID: <81bfc67a0902270127r1c0dbd6du3bd840bbfdd4aa5e@mail.gmail.com> Subject: Re: [gentoo-dev] Collecting opinions about GLEP 55 and alternatives From: Caleb Cushing To: gentoo-dev@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: dec95c7d-9e02-4918-8acb-ec73b7eb4aa1 X-Archives-Hash: 12be928e758421c2191c7476f78a25fd On Tue, Feb 24, 2009 at 5:21 PM, Petteri R=C3=A4ty = wrote: > My notes so far: > > 1) Status quo > =C2=A0- does not allow changing inherit > =C2=A0- bash version in global scope > =C2=A0- global scope in general is quite locked down > > 2) EAPI in file extension > =C2=A0- Allows changing global scope and the internal format of the ebuil= d > =C2=A0a) .ebuild- > =C2=A0 =C2=A0- ignored by current Portage > =C2=A0b) ..ebuild > =C2=A0 =C2=A0- current Portage does not work with this > =C2=A0c) .. > =C2=A0 =C2=A0- ignored by current Portage > > 3) EAPI in locked down place in the ebuild > =C2=A0- Allows changing global scope > =C2=A0- EAPI can't be changed in an existing ebuild so the PM can trust > =C2=A0 =C2=A0the value in the cache > =C2=A0- Does not allow changing versioning rules unless version becomes a > =C2=A0 =C2=A0normal metadata variable > =C2=A0 =C2=A0* Needs more accesses to cache as now you don't have to load= older > =C2=A0 =C2=A0 =C2=A0versions if the latest is not masked > =C2=A0a) > =C2=A0b) new subdirectory like ebuilds/ > =C2=A0- we could drop extension all together so don't have to argue about > =C2=A0 =C2=A0it any more > =C2=A0- more directory reads to get the list of ebuilds in a repository > =C2=A0c) .ebuild in current directory > =C2=A0- needs one year wait > I don't see the point of some of these... a shorter extension would be nice but not really necessary. ..ebuild so like .2.ebuild 'cause that'd work great? smith-1.3.6.2.ebuild better yet vanilla-sources-2.6.28.2.2.ebuild yeah I can see that working out... no it wouldn't or maybe smith-1.3.6.eapi-2.ebuild just too long here's an idea, perhaps not a great one... but perhaps it'll make someone else think... how about this on the first line # eapi-2 and instead of sourcing it, have portage match it with a regex first, figure out the eapi, then source it. I don't know if I really like like what I'm proposing, but I don't see anything else that looks good. --=20 Caleb Cushing http://xenoterracide.blogspot.com