Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: is the PRIORITY variable actually used anywhere?
Date: Mon, 2 Jul 2012 07:29:08 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1207020726170.23135@oneiric> (raw)
In-Reply-To: <1341219932.23146.187.camel@ted>

On Mon, 2 Jul 2012, Richard Purdie wrote:

> On Sat, 2012-06-30 at 06:20 -0400, Robert P. J. Day wrote:
> > On Sat, 30 Jun 2012, Martin Jansa wrote:
> >
> > > http://git.openembedded.org/meta-openembedded/commit/?id=040f75eca217c79fed7b881589d9bb36358cffe1
> > > http://git.openembedded.org/openembedded-core/commit/?id=d122343362669c683acc4af295971a62cbc823fc
> > >
> > > so can be dropped from bitbake.conf too AFAIK
> >
> >   actually, there are still a number of lines that refer to that
> > variable:
> >
> > $ grep -rw PRIORITY *
> > meta/conf/bitbake.conf:PRIORITY = "optional"
> > meta/conf/documentation.conf:PRIORITY[doc] = "Importance of package, default values are 'optional' or 'needed'."
> > meta/classes/package_deb.bbclass:        fields.append(["Priority: %s\n", ['PRIORITY']])
> > meta/classes/package_ipk.bbclass:		fields.append(["Priority: %s\n", ['PRIORITY']])
> > meta/classes/oelint.bbclass:	# Test for valid PRIORITY
> > meta/classes/oelint.bbclass:	s = testVar("PRIORITY")
> > meta/classes/oelint.bbclass:				bb.note("PRIORITY '%s' is not recommended" % s)
> > meta/classes/oelint.bbclass:				bb.note("PRIORITY '%s' is not recommended, better use '%s'" % (s, newprio))
> > meta/classes/oelint.bbclass:			bb.note("PRIORITY '%s' is not recommended" % s)
> > meta/classes/oelint.bbclass:			bb.error("PRIORITY should only use lower case")
> > $
> >
> >   if i can assume that all of that can be removed, i can do that as a
> > single patch, again unless someone else wants to handle it if there
> > are subtleties involved.
>
> I think this one is best left alone as the code stands. We did remove
> the variable from standard usage, it doesn't obsolete the above code
> which someone could in theory still use from say a distro configuration
> perspective.
>
> The line in documentation.conf look wrong though, I think "needed"
> should be "required".

  oelint.bbclass currently suggests it can be any of "standard",
"required", "optional" or "extra".  and perhaps a dumb question -- how
are there *two* default values?  not sure what that means.

  anyway, i'll leave this in someone else's capable hands.  it's
pretty obvious that no use is being made of this variable these days.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================



  reply	other threads:[~2012-07-02 11:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-30 10:02 is the PRIORITY variable actually used anywhere? Robert P. J. Day
2012-06-30 10:07 ` Martin Jansa
2012-06-30 10:17   ` Robert P. J. Day
2012-06-30 10:20   ` Robert P. J. Day
2012-07-02  9:05     ` Richard Purdie
2012-07-02 11:29       ` Robert P. J. Day [this message]
2012-07-02 12:10         ` Paul Eggleton
2012-07-02 12:12           ` Robert P. J. Day
2012-07-02 13:14         ` Richard Purdie

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=alpine.DEB.2.02.1207020726170.23135@oneiric \
    --to=rpjday@crashcourse.ca \
    --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