From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: [gentoo-pms] Why do we have mandatory ebuild variables?
Date: Sun, 15 Jul 2012 15:57:05 +0200 [thread overview]
Message-ID: <20482.52273.749308.173776@a1i15.kph.uni-mainz.de> (raw)
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
next reply other threads:[~2012-07-15 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 13:57 Ulrich Mueller [this message]
2012-07-21 20:11 ` [gentoo-pms] Re: Why do we have mandatory ebuild variables? Ulrich Mueller
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=20482.52273.749308.173776@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-pms@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