public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] repoman: add --straight-to-stable (-S) option
Date: Tue, 24 Mar 2015 11:06:50 -0700	[thread overview]
Message-ID: <5511A7BA.80207@gentoo.org> (raw)
In-Reply-To: <1427188244-27377-1-git-send-email-mgorny@gentoo.org>

On 03/24/2015 02:10 AM, Michał Górny wrote:
> Add an option to safely allow committing ebuilds straight to stable.
> Before, this required either round trips with multiple commits or
> --force option that ignored valid QA concerns and (surprisingly to many
> developers) skipped some expensive QA checks.
> ---
>  bin/repoman | 28 ++++++++++++++++------------
>  1 file changed, 16 insertions(+), 12 deletions(-)
> 
> diff --git a/bin/repoman b/bin/repoman
> index 13c220d..03664bd 100755
> --- a/bin/repoman
> +++ b/bin/repoman
> @@ -191,6 +191,9 @@ def ParseArgs(argv, qahelp):
>  	parser.add_argument('-f', '--force', dest='force', default=False, action='store_true',
>  		help='Commit with QA violations')
>  
> +	parser.add_argument('-S', '--straight-to-stable', dest='straight_to_stable', default=False,
> +		action='store_true', help='Allow committing straight to stable')
> +
>  	parser.add_argument('--vcs', dest='vcs',
>  		help='Force using specific VCS instead of autodetection')
>  
> @@ -1908,18 +1911,19 @@ for x in effective_scanlist:
>  				(relative_path, len(myaux['DESCRIPTION']), max_desc_len))
>  
>  		keywords = myaux["KEYWORDS"].split()
> -		stable_keywords = []
> -		for keyword in keywords:
> -			if not keyword.startswith("~") and \
> -				not keyword.startswith("-"):
> -				stable_keywords.append(keyword)
> -		if stable_keywords:
> -			if ebuild_path in new_ebuilds and catdir != "virtual":
> -				stable_keywords.sort()
> -				stats["KEYWORDS.stable"] += 1
> -				fails["KEYWORDS.stable"].append(
> -					x + "/" + y + ".ebuild added with stable keywords: %s" % \
> -						" ".join(stable_keywords))
> +		if not options.straight_to_stable:
> +		    stable_keywords = []
> +		    for keyword in keywords:
> +			    if not keyword.startswith("~") and \
> +				    not keyword.startswith("-"):
> +				    stable_keywords.append(keyword

The indents above mix spaces with tabs.

> +		    if stable_keywords:
> +			    if ebuild_path in new_ebuilds and catdir != "virtual":
> +				    stable_keywords.sort()
> +				    stats["KEYWORDS.stable"] += 1
> +				    fails["KEYWORDS.stable"].append(
> +					    x + "/" + y + ".ebuild added with stable keywords: %s" % \
> +						    " ".join(stable_keywords))

In this scope, the relative_path variable is equivalent to x + "/" + y +
".ebuild", so you could use that instead.

>  
>  		ebuild_archs = set(kw.lstrip("~") for kw in keywords \
>  			if not kw.startswith("-"))
> 


-- 
Thanks,
Zac


  reply	other threads:[~2015-03-24 18:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24  9:10 [gentoo-portage-dev] [PATCH] repoman: add --straight-to-stable (-S) option Michał Górny
2015-03-24 18:06 ` Zac Medico [this message]
2015-03-25  8:12   ` [gentoo-portage-dev] [PATCH v2] " Michał Górny
2015-03-25 17:05     ` Brian Dolbec

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=5511A7BA.80207@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-portage-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