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.77) (envelope-from ) id 1SqPKA-0007Ly-9b for garchives@archives.gentoo.org; Sun, 15 Jul 2012 13:57:26 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8A2EF21C005; Sun, 15 Jul 2012 13:57:14 +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 9E84721C005 for ; Sun, 15 Jul 2012 13:57:12 +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 q6FDvBAd002726 for ; Sun, 15 Jul 2012 15:57:11 +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 q6FDvB5F031067; Sun, 15 Jul 2012 15:57:11 +0200 Received: (from ulm@localhost) by a1i15.kph.uni-mainz.de (8.14.5/8.14.5/Submit) id q6FDvBZq031064; Sun, 15 Jul 2012 15:57:11 +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: <20482.52273.749308.173776@a1i15.kph.uni-mainz.de> Date: Sun, 15 Jul 2012 15:57:05 +0200 To: gentoo-pms@lists.gentoo.org Subject: [gentoo-pms] Why do we have mandatory ebuild variables? X-Mailer: VM 8.2.0b under 23.4.2 (x86_64-pc-linux-gnu) From: Ulrich Mueller X-Archives-Salt: d4cb3e55-3944-41c6-9189-d628db200744 X-Archives-Hash: d30fdf0df4375235506a1f52fa02cde6 PMS says that seven variables (DESCRIPTION, HOMEPAGE, SRC_URI, LICENSE, SLOT, KEYWORDS, IUSE) are mandatory in ebuilds. In bug 425848 and in #gentoo-portage the question arose why this is needed. For example, many live ebuilds don't define SRC_URI or KEYWORDS, and package managers seem to have no problem with it. (?) Virtuals could profit if they wouldn't have to define variables like HOMEPAGE, SRC_URI, and LICENSE that are meaningless for them. Could we loosen this requirement for the variables that are allowed to be empty (i.e. all except DESCRIPTION and SLOT), or would this cause any trouble with package managers? For EAPI 5, or retroactively? Ulrich