Bug#1027832: debian-policy: Please clarify that priority required packages are not automatically build essential

[Bill Allombert <ballombe@debian.org>]

On Wed, Jan 04, 2023 at 08:46:39AM +0100, Santiago Vila wrote:
> El 4/1/23 a las 2:32, Sam Hartman escribió:
> > > > > > > "Santiago" == Santiago Vila <sanvila@debian.org> writes:
> > 
> >      Santiago> As an example, packages tzdata, mount or e2fsprogs are not
> >      Santiago> build-essential and afaik have not been for a long time,
> >      Santiago> but there are still people who believe that they are
> >      Santiago> build-essential for the mere fact that they are
> >      Santiago> priority:required.
> > 
> > Why not just make all required packages build-essential?
> > I agree we should fix the class of bugs you are talking about, but it
> > seems like in some cases it might be easier to fix them by declaring
> > them not buggy.
> 
> Because required to build != required in a _running_ system

At minimum, it should not be allowed to Build-Conflicts with a required package.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here.