Ansgar wrote:
> could we drop the Priority field from most packages? Most packages use
> "Priority: optional" and this is just noise in d/control (source
> package). Tools should just assume "optional" when no other value is
> set.
This seems like a great idea. People regularly note the overhead o
Ansgar:
Hi,
could we drop the Priority field from most packages? Most packages use
"Priority: optional" and this is just noise in d/control (source
package). Tools should just assume "optional" when no other value is
set.
[...]
I would like to drop it pretty much everywhere, most importantly
d
On Sat, 13 May 2023 at 16:13, Ansgar wrote:
>
> Hi,
>
> could we drop the Priority field from most packages? Most packages use
> "Priority: optional" and this is just noise in d/control (source
> package). Tools should just assume "optional" when no other value is
> set.
>
> Currently Policy docum
Hi,
could we drop the Priority field from most packages? Most packages use
"Priority: optional" and this is just noise in d/control (source
package). Tools should just assume "optional" when no other value is
set.
Currently Policy documents Priority to be mandatory in 2.5:
+---
| Each package mu
4 matches
Mail list logo
