From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Don't require assignment of empty variables in ebuilds?
Date: Wed, 25 Jul 2012 12:00:39 -0400 [thread overview]
Message-ID: <201207251200.39910.vapier@gentoo.org> (raw)
In-Reply-To: <20486.63521.223740.628410@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: Text/Plain, Size: 877 bytes --]
On Wednesday 18 July 2012 13:53:37 Ulrich Mueller wrote:
> 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.
i think we should clarify and say that when an eclass provides these, the
ebuild need not. completely missing DESCRIPTION/HOMEPAGE should be a warning
(and maybe KEYWORDS), and LICENSE should be an error. there are plenty of
examples of SRC_URI not being set and that's fine (live ebuilds, ebuilds that
only install out of $FILESDIR, virtuals, etc...).
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-07-25 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 17:53 [gentoo-dev] Don't require assignment of empty variables in ebuilds? Ulrich Mueller
2012-07-18 18:02 ` Robin H. Johnson
2012-07-18 18:11 ` Davide Pesavento
2012-07-25 16:00 ` Mike Frysinger [this message]
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=201207251200.39910.vapier@gentoo.org \
--to=vapier@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