From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Don't require assignment of empty variables in ebuilds?
Date: Wed, 08 Aug 2012 19:04:43 -0700 [thread overview]
Message-ID: <50231ABB.40501@gentoo.org> (raw)
In-Reply-To: <20496.8429.216032.904090@a1i15.kph.uni-mainz.de>
On 07/25/2012 09:38 AM, Ulrich Mueller wrote:
> On the other hand, tree policy (as enforced by repoman) wouldn't
> really change. In the cases you've mentioned above, it already
> displays errors or warnings. Repoman also doesn't distinguish between
> empty and unset variables. 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.
IUSE.undefined is removed in Portage git:
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=f7ec7a4db6543e1fd3a13c341a37ccb667956978
--
Thanks,
Zac
prev parent reply other threads:[~2012-08-09 2:05 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
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 [this message]
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=50231ABB.40501@gentoo.org \
--to=zmedico@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