public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] 'stricter' FEATURE and "poor programming practices" notice
Date: Thu, 17 May 2007 12:50:23 -0700	[thread overview]
Message-ID: <464CB1FF.80407@gentoo.org> (raw)
In-Reply-To: <1179400321.5388.5.camel@ip6-localhost>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hans de Graaff wrote:
> If the notice is only informational, then the emerge process should not
> be stopped because of it (and this would mean that it is nice to fix
> these issues but not mandatory).

If you disable stricter in FEATURES, you'll still get the same
informational message, but the install will continue.  The messages
will be logged if you add qa to PORTAGE_ELOG_CLASSES (see
make.conf.example).  If you only want to exempt specific packages
from the stricter behavior, you can put something like this in
/etc/portage/bashrc:

[ "${CATEGORY}/${PN}" == "app-foo/bar" ] && \
	export FEATURES=${FEATURES/stricter/}

Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (GNU/Linux)

iD8DBQFGTLH9/ejvha5XGaMRAu/OAJ9AiTgbY6elQrYxlymy1TL1cLzc+wCgw12T
9uxK1MTeBOqmPtZBwyqOVms=
=ax5j
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2007-05-17 19:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-17 11:12 [gentoo-dev] 'stricter' FEATURE and "poor programming practices" notice Hans de Graaff
2007-05-17 11:23 ` Ciaran McCreesh
2007-05-18  3:05   ` [gentoo-dev] " Ryan Hill
2007-05-17 19:50 ` Zac Medico [this message]
2007-05-19 15:32 ` [gentoo-dev] " Kevin F. Quinn

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=464CB1FF.80407@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