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

Bug#819660: explicitly allow building automatic debug symbols packages not listed in control



Tanguy Ortolo <tanguy+debian@ortolo.eu> writes:

> The Policy implicitly indicates a source package should only build
> binary packages listed in debian/control. At least, this is how
> ftpmaster interprets §5.2, 5.4 and 5.6.19, when you look at the Reject
> FAQ <https://ftp-master.debian.org/REJECT-FAQ.html> (search for
> “debian/control breakage #2”).

> Now, this is quite not compatible with the new debug symbol packages
> <https://wiki.debian.org/AutomaticDebugPackages> that are now
> automatically created.

> Since explicit is better than implicit, I think §5.2:

>>The debian/control file contains the most vital (and
>>version-independent) information about the source package and about the
>>binary packages it creates.
>>
>>The first paragraph of the control file contains information about the
>>source package in general. The subsequent sets each describe a binary
>>package that the source tree builds.

> could be completed by:

>>[…]
>>
>>The first paragraph of the control file contains information about the
>>source package in general. The subsequent sets each describe a binary
>>package that the source tree builds. All the binary packages have a
>>corresponding paragraph, except for the possible automatic debug
>>packages that do not require one.

> There may be better ways to phrase this, but I think there is still a
> need for some clarification about this.

Seems reasonable to me.  Seconded.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>


Reply to: