Bug#1029831: debian-policy: Make required packages build-essential
Package: debian-policy
[ This is basically #1027832 ]
Timo Röhling writes:
> * Andreas Henriksson <andreas@fatal.se> [2023-01-28 12:50]:
>>Policy is not a religion. Policy has many bugs. Policy is very outdated.
>>[...]
>>Here's an example you could follow:
>>https://lists.debian.org/debian-policy/2022/12/msg00023.html
> Your argument cuts both ways. Right now, Policy says that
> the bugs are RC, and if you believe that should be different, why
> don't you propose such a change and seek consensus yourself?
I don't think it does. Policy doesn't specify what packages actually
are build-essential; it only refers to an "informational list" in
Section 4.2.
I think discussion in #1027832 suggested that required packages should
be build-essential as well. Maybe this should be made explicit, for
example by changing
+---
| The required packages are called build-essential, and an informational
| list can be found in /usr/share/doc/build-essential/list (which is
| contained in the build-essential package).
+---[ Section 4.2 ]
to something like
+---
| The required packages are called build-essential, and include packages
| with Priority "required" and additional packages. An informational
| list of additional packages can be found in
| /usr/share/doc/build-essential/list (which is contained in the
| build-essential package).
+---
This only documents existing practice as practically all systems have
required packages installed.
Ansgar
Reply to: