From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] base: Make PRINC warning an error
Date: Wed, 5 Nov 2014 13:18:34 -0600 [thread overview]
Message-ID: <545A780A.2070706@windriver.com> (raw)
In-Reply-To: <1415212983.23396.57.camel@ted>
On 11/5/14, 12:43 PM, Richard Purdie wrote:
> Apparently 1.5 years of warnings isn't enough to get anyone to take any
> notice. We therefore make this an error so people can ignore it for
> another 6 months whereafter we can finally give up and remove the
> obsolete code.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
> index e1b25ff..f5b216b 100644
> --- a/meta/classes/base.bbclass
> +++ b/meta/classes/base.bbclass
> @@ -375,7 +375,7 @@ python () {
> # obsolete. Return a warning to the user.
> princ = d.getVar('PRINC', True)
> if princ and princ != "0":
> - bb.warn("Use of PRINC %s was detected in the recipe %s (or one of its .bbappends)\nUse of PRINC is deprecated. The PR server should be used to automatically increment the PR. See: https://wiki.yoctoproject.org/wiki/PR_Service." % (princ, d.getVar("FILE", True)))
> + bb.error("Use of PRINC %s was detected in the recipe %s (or one of its .bbappends)\nUse of PRINC is deprecated. The PR server should be used to automatically increment the PR. See: https://wiki.yoctoproject.org/wiki/PR_Service." % (princ, d.getVar("FILE", True)))
> pr = d.getVar('PR', True)
> pr_prefix = re.search("\D+",pr)
> prval = re.search("\d+",pr)
>
>
I'd suggest removing the code -after- the bb.error as well..
Make it an error.. and remove the functionality so it's -clear- you can't just
make it a warning again.
--Mark
prev parent reply other threads:[~2014-11-05 19:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 18:43 [PATCH] base: Make PRINC warning an error Richard Purdie
2014-11-05 19:18 ` Mark Hatle [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=545A780A.2070706@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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