Received: from cpanel7.indieserve.net (cpanel7.indieserve.net [199.212.143.8]) by mx.groups.io with SMTP id smtpd.web11.56934.1584980896078850769 for ; Mon, 23 Mar 2020 09:28:16 -0700 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: crashcourse.ca, ip: 199.212.143.8, mailfrom: rpjday@crashcourse.ca) Received: from cpeac202e043973-cmac202e043970.sdns.net.rogers.com ([174.114.100.179]:49810 helo=localhost.localdomain) by cpanel7.indieserve.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1jGPvy-0072yg-D2; Mon, 23 Mar 2020 12:28:15 -0400 Date: Mon, 23 Mar 2020 12:28:12 -0400 (EDT) From: "rpjday@crashcourse.ca" X-X-Sender: rpjday@localhost.localdomain To: Richard Purdie cc: OE Core mailing list Subject: Re: [OE-core] what is the current purpose of PRIORITY variable? In-Reply-To: <534b0df5f09c60381ed520ff3f840a1b315d3142.camel@linuxfoundation.org> Message-ID: References: <89ed530a5dc904f8ea677e2633f3732b59b3bbc8.camel@linuxfoundation.org> <534b0df5f09c60381ed520ff3f840a1b315d3142.camel@linuxfoundation.org> MIME-Version: 1.0 X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cpanel7.indieserve.net X-AntiAbuse: Original Domain - lists.openembedded.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - crashcourse.ca X-Get-Message-Sender-Via: cpanel7.indieserve.net: authenticated_id: rpjday+crashcourse.ca/only user confirmed/virtual account not confirmed X-Authenticated-Sender: cpanel7.indieserve.net: rpjday@crashcourse.ca X-Source: X-Source-Args: X-Source-Dir: Content-Type: text/plain; charset=US-ASCII On Mon, 23 Mar 2020, Richard Purdie wrote: > On Mon, 2020-03-23 at 12:06 -0400, Robert P. J. Day wrote: > > 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? > > I'm torn on that. The Priority field is a standard part of a debian > package ( > https://www.debian.org/doc/manuals/debian-faq/ch-pkg_basics.en.html#s-priority > ) and also part of opkg's implementation. > > We don't use it, I'm not sure that means we should remove the code > which would allow someone to though. > > I also don't know if dpkg/apt supports an unset value for it. ok, i'll pass on that and move on, there's plenty of other stuff to work on. rday