From: "rpjday@crashcourse.ca" <rpjday@crashcourse.ca>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] what is the current purpose of PRIORITY variable?
Date: Mon, 23 Mar 2020 12:06:59 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.2003231206180.20339@localhost.localdomain> (raw)
In-Reply-To: <89ed530a5dc904f8ea677e2633f3732b59b3bbc8.camel@linuxfoundation.org>
On Mon, 23 Mar 2020, Richard Purdie wrote:
> On Mon, 2020-03-23 at 09:28 -0400, rpjday@crashcourse.ca wrote:
> > continuing my travels, ran across "PRIORITY" variable that i was
> > not
> > aware of, was introduced in bitbake.conf way back in 2005 in
> > oelint.bbclass, but there are only a few lonely references to it
> > these days:
> >
> > meta/conf/documentation.conf:PRIORITY[doc] = "Indicates the
> > importance
> > of a package. The default value is 'optional'. Other standard
> > values
> > are 'required', 'standard' and 'extra'."
> >
> > meta/conf/bitbake.conf:PRIORITY = "optional"
> >
> > meta/classes/package_ipk.bbclass: fields.append(["Priority:
> > %s\n", ['PRIORITY']])
> >
> > meta/classes/package_ipk.bbclass:IPKEXTRAVARS = "PRIORITY MAINTAINER
> > PACKAGE_ARCH HOMEPAGE"
> >
> > meta/classes/package_deb.bbclass: fields.append(["Priority:
> > %s\n", ['PRIORITY']])
> >
> > meta/classes/package_deb.bbclass:do_package_write_deb[vardeps] +=
> > "PKGV PKGR PKGV DESCRIPTION SECTION PRIORITY MAINTAINER DPKG_ARCH PN
> > HOMEPAGE"
> >
> > is this doing anything useful these days?
>
> Not really, no.
any objection to my submitting a patch to remove it?
rday
next prev parent reply other threads:[~2020-03-23 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 13:28 what is the current purpose of PRIORITY variable? rpjday
2020-03-23 16:05 ` [OE-core] " Richard Purdie
2020-03-23 16:06 ` rpjday [this message]
2020-03-23 16:11 ` Richard Purdie
2020-03-23 16:28 ` rpjday
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.LFD.2.21.2003231206180.20339@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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