what is the current purpose of PRIORITY variable?
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?
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================Quoted 20 lines · On Mon, 2020-03-23 at 09:28 -0400, [email protected] 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_ARCHHOMEPAGE"
Quoted 8 lines
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_ARCHPN HOMEPAGE"is this doing anything useful these days?
Not really, no.
Cheers,
Richard
Quoted 24 lines · Richard Purdie
Quoted 23 lines · On Mon, 2020-03-23 at 09:28 -0400, [email protected] 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_ARCHHOMEPAGE"meta/classes/package_deb.bbclass: fields.append(["Priority:
%s\n", ['PRIORITY']])
Quoted 7 lines
Quoted 5 lines
meta/classes/package_deb.bbclass:do_package_write_deb[vardeps] += "PKGV PKGR PKGV DESCRIPTION SECTION PRIORITY MAINTAINER
DPKG_ARCHPN HOMEPAGE"is this doing anything useful these days?
Not really, no.
any objection to my submitting a patch to remove it?
rday
Quoted 35 lines · Robert P. J. Day
Quoted 33 lines · Richard Purdie
Quoted 32 lines · On Mon, 2020-03-23 at 09:28 -0400, [email protected] 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_ARCHHOMEPAGE"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_ARCHPN
HOMEPAGE"
Quoted 5 lines
Quoted 3 lines
Quoted 1 line
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.
Cheers,
Richard
Quoted 47 lines · Richard Purdie
Quoted 35 lines · Robert P. J. Day
Quoted 33 lines · Richard Purdie
Quoted 32 lines · On Mon, 2020-03-23 at 09:28 -0400, [email protected] 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_ARCHHOMEPAGE"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_ARCHPN
HOMEPAGE"Quoted 5 lines
Quoted 3 lines
Quoted 1 line
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.
Quoted 4 lines
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