From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Don't require assignment of empty variables in ebuilds?
Date: Wed, 18 Jul 2012 19:53:37 +0200 [thread overview]
Message-ID: <20486.63521.223740.628410@a1i15.kph.uni-mainz.de> (raw)
Our current policy [1] requires that ebuilds must assign the seven
variables DESCRIPTION, HOMEPAGE, SRC_URI, LICENSE, SLOT, KEYWORDS, and
IUSE, even if their value is empty.
Could we drop this requirement? Repoman already enforces that
DESCRIPTION, HOMEPAGE, LICENSE, SLOT, and KEYWORDS are non-empty
(with some exceptions for virtuals). I don't see why we need to
distinguish the "empty value" and "not assigned" cases.
For example, many live ebuilds already don't define SRC_URI. I'm not
aware of any problems caused by this.
Ulrich
[1] <http://devmanual.gentoo.org/ebuild-writing/variables/#required-variables>
next reply other threads:[~2012-07-18 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 17:53 Ulrich Mueller [this message]
2012-07-18 18:02 ` [gentoo-dev] Don't require assignment of empty variables in ebuilds? Robin H. Johnson
2012-07-18 18:11 ` Davide Pesavento
2012-07-25 16:00 ` Mike Frysinger
2012-07-25 16:38 ` Ulrich Mueller
2012-07-25 16:56 ` Pacho Ramos
2012-07-25 17:05 ` Rick "Zero_Chaos" Farina
2012-07-25 18:15 ` Michał Górny
2012-07-25 18:32 ` Mike Frysinger
2012-08-09 2:04 ` Zac Medico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20486.63521.223740.628410@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox