From: Pacho Ramos <pacho@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 18:56:23 +0200 [thread overview]
Message-ID: <1343235384.22460.0.camel@belkin4> (raw)
In-Reply-To: <20496.8429.216032.904090@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 235 bytes --]
El mié, 25-07-2012 a las 18:38 +0200, Ulrich Mueller escribió:
[...]
> The single exception to this is IUSE, which
> is required to be present in an ebuild even if it's empty. Maybe we
> should drop this requirement, too.
+1
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-07-25 16:57 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
2012-07-25 16:38 ` Ulrich Mueller
2012-07-25 16:56 ` Pacho Ramos [this message]
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=1343235384.22460.0.camel@belkin4 \
--to=pacho@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