From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A1FF5138010 for ; Sun, 30 Sep 2012 09:13:44 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 79E2B21C025; Sun, 30 Sep 2012 09:13:35 +0000 (UTC) Received: from a1iwww1.kph.uni-mainz.de (a1iwww1.kph.uni-mainz.de [134.93.134.1]) by pigeon.gentoo.org (Postfix) with ESMTP id EA07121C025 for ; Sun, 30 Sep 2012 09:13:33 +0000 (UTC) Received: from a1i15.kph.uni-mainz.de (a1i15.kph.uni-mainz.de [134.93.134.92]) by a1iwww1.kph.uni-mainz.de (8.14.4/8.13.4) with ESMTP id q8U9DW5B020436; Sun, 30 Sep 2012 11:13:32 +0200 Received: from a1i15.kph.uni-mainz.de (localhost [127.0.0.1]) by a1i15.kph.uni-mainz.de (8.14.5/8.14.2) with ESMTP id q8U9DVeX002111; Sun, 30 Sep 2012 11:13:31 +0200 Received: (from ulm@localhost) by a1i15.kph.uni-mainz.de (8.14.5/8.14.5/Submit) id q8U9DVki002107; Sun, 30 Sep 2012 11:13:31 +0200 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Package Manager Specification discussions X-BeenThere: gentoo-pms@gentoo.org X-BeenThere: gentoo-pms@lists.gentoo.org Reply-To: gentoo-pms@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20584.3387.660954.8184@a1i15.kph.uni-mainz.de> Date: Sun, 30 Sep 2012 11:13:31 +0200 To: gentoo-pms@lists.gentoo.org Cc: Brian Harring Subject: Re: [gentoo-pms] [PATCH] EAPI must be at least a single char. In-Reply-To: <1348993716-27744-1-git-send-email-ferringb@gmail.com> References: <1348993716-27744-1-git-send-email-ferringb@gmail.com> X-Mailer: VM 8.2.0b under 23.4.2 (x86_64-pc-linux-gnu) From: Ulrich Mueller X-Archives-Salt: f41fabdf-1477-4112-be9a-7402b4e61d64 X-Archives-Hash: fb6d589f64499d246398f48f1ca2ee7d >>>>> On Sun, 30 Sep 2012, Brian Harring wrote: > The example regex allowed for > EAPI= > Which isn't used, alloewd, nor desired; at best, that's short hand > for EAPI=0. The regexp was never meant to match exactly what is allowed. It matches a superset, and if the matched substring turns out to be an illegal or unknown EAPI, then the PM can catch it after parsing. Otherwise, an empty EAPI is already forbidden by section 3.1 "Restrictions upon Names". Ulrich