Hi.

The Homepage control filed is according to chapter 5.2 allowed in both,
the source package and the binary packages paragraphs.

IMHO, this makes (semantically even sense - perhaps that should be pointed out,
too) as e.g. a -doc, or a -dev packacke might have it's own bigger area
in the whole project's website.

But unlike with Section and Priority, it's not specified whether the binary packages
derive that from the Source package if it's specified there AND not overriden
in the binary package paragraph.

HTH,
Chris.

It's treated likewise.

It's also documented in a new manual page called "deb-src-control(5)" that
is currently only in dpkg's git repository:
http://git.debian.org/?p=dpkg/dpkg.git;a=blob;f=man/deb-src-control.5

It will thus be documented in wheezy's dpkg.

Cheers,

Great...

Nevertheless,.. speaks anything against adding that sentence to the
policy, as already done with Priority/Section?


Thx,
Chris.

user debian-policy@packages.debian.org
severity 609935 minor
clone 609935 -1
retitle -1 policy: clarify precedence and propagation of Section and Priority
usertags 609935 + informative issue
usertags -1 + informative issue
quit

Hi,

Christoph Anton Mitterer wrote:
[...]

Here's a survey of the current status.  I'll focus on Priority, since
Section uses almost identical constructions.

 §2.5 Priorities:
	Each package should have a priority value, which is included
	in the package's control record (see Priority, Section 5.6.6).

 §5.6.6 Priority:
	When it appears in the debian/control file, it gives the value
	for the subfield of the same name in the Files field of the
	.changes file. It also gives the default for the same field in
	the binary packages.

When it appears in the first (general) paragraph of debian/control or
a package-specific paragraph?  And does it give the default for the
package-specific paragraph or the corresponding field of
DEBIAN/control?

Unless I'm missing something, the text could be a lot clearer.
Thanks for a pointer.

Regards,
Jonathan