[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Fw: control file: Priority for udeb packages



Forgot to add you to CC

Holger




Date: Mon, 7 Jan 2019 23:10:01 +0100
From: Holger Wansing <hwansing@mailbox.org>
To: debian-boot <debian-boot@lists.debian.org>
Subject: control file: Priority for udeb packages


Hi,

the Debian Policy is not strict there under
https://www.debian.org/doc/debian-policy/ch-controlfields.html#priority
so I better ask:

Is there any sense in adding a Priority field for udeb packages? 
For example like this for cdebconf:


----snip---------------
Source: cdebconf
Section: utils
Priority: optional
[...]

Package: cdebconf
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, debconf, dpkg (>= 1.15.4)
Provides: debconf-2.0
Suggests: cdebconf-gtk
Priority: optional
[...]

Package: cdebconf-udeb
Architecture: any
Section: debian-installer
Priority: standard
Depends: ${shlibs:Depends}, ${misc:Depends}
Provides: debconf-2.0
Package-Type: udeb
[...]

------snap-----------------


Source package has optional, also has the 'cdebconf' binary package, and the
udeb has standard.
I this somehow intended? Has is some effect?

udebs are 'micro binary packages' by definition, so they don't need the
Priority field themselves, they inherit the value from Source package, right?

Any other intention, especially why the udeb has standard, while source has
optional?


Holger



-- 
Holger Wansing <hwansing@mailbox.org>
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



-- 
Holger Wansing <hwansing@mailbox.org>
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076


Reply to: