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

Bug#998165: debian-policy: document and allow Description in the source paragraph



Hello Guillem, Mattia,

On Fri 24 Dec 2021 at 01:42PM +01, Guillem Jover wrote:

> On Tue, 2021-12-21 at 17:53:31 -0700, Sean Whitton wrote:
>>
>> Is there really no name for the first paragraph other than "general
>> paragraph"?
>
> That's how the dpkg documentation (man and perl modules POD) refers to
> it (or first block of information, which is even worse), but I agree
> it's rather suboptimal, and I'd like to get a better name for it. See
> below.

Okay, fair enough, then let's just use "general paragraph" for now.

> For example we have «Debian source control file» or «Debian source
> packages' control file» for .dsc, then we have «Source package control
> file» or in dpkg «Debian source packages' master control file» for
> debian/control. Which are almost the same. I've been considering naming
> debian/control something like «Debian template source control file», as
> that is used to generate both the source and binary control files.
>
> But I think I'll open a new bug to cover and discuss that.

Cool.

>> Also, how about "the text in this field describes all binary packages
>> which do not have their own Description: fields" ?
>
> I'm not sure whether you are (or the text would then) imply this; but
> the Description in the source stanza does not get inherited by the
> binary stanzas when generating the binary package control file, one
> needs to add references to it via substvars.

Oh, right.

In that case, returning to Mattia's patch, it is probably not correct to
say that the source Description is relevant for all binary packages,
because perhaps the substvar is used for some but not all of them?

-- 
Sean Whitton

Attachment: signature.asc
Description: PGP signature


Reply to: