public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] revdep-rebuild bikeshedding
Date: Wed, 16 Jan 2013 15:57:22 -0500	[thread overview]
Message-ID: <50F71432.7030203@gentoo.org> (raw)
In-Reply-To: <50F710FC.6070200@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 16/01/13 03:43 PM, Paul Varner wrote:
> All:
> 
> Time for some bikeshedding :)
> 
> For the gentoolkit-0.3.0 series, I removed any filtering of emerge 
> options set in EMERGE_DEFAULT_OPS for revdep-rebuild.  This has
> caused some people to complain because some of the flags in their 
> EMERGE_DEFAULT_OPTS are not suitable for a revdep-rebuild run.
> 
> I am not going to go back to filtering any of the emerge options, 
> however, I just added support for a make.conf variable called 
> REVDEP_DEFAULT_OPTS which currently gets appended to the list of
> options after the EMERGE_DEFAULT_OPTS and before the command line
> options.
> 
> Here is where the bikeshedding begins: 1. What variable name do we
> prefer? REVDEP_DEFAULT_OPTS or REVDEP_EMERGE_DEFAULT_OPTS

+1 on REVDEP_DEFAULT_OPTS , but if things are going to be verbose
might as well make them completely verbose with
REVDEP_REBUILD_DEFAULT_EMERGE_OPTS

> 2. What behavior do we want? append to EMERGE_DEFAULT_OPTS or
> replace EMERGE_DEFAULT_OPTS

+1 on the replace.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iF4EAREIAAYFAlD3FDIACgkQ2ugaI38ACPC3gQEAvUlApXInabHifnIXlqsUJhJX
syeaaDkOXLzSO1L3vskA/2xX2YxAMnnmtFkv+QLBi+Kx+fLi60ZE/0QD1Zd5LH/3
=h5CO
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2013-01-16 20:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 20:43 [gentoo-dev] revdep-rebuild bikeshedding Paul Varner
2013-01-16 20:52 ` Rich Freeman
2013-01-16 20:57 ` Ian Stakenvicius [this message]
2013-01-16 21:52   ` Albert Hopkins
2013-01-17 10:25 ` Sergey Popov

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=50F71432.7030203@gentoo.org \
    --to=axs@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