Chapter 5. Control files and their fields

31

5.6.4

Changed By

The name and email address of the person who changed the said package. Usually the name

of the maintainer. All the rules for the Maintainer field apply here, too.

5.6.5

Section

This field specifies an application area into which the package has been classified. See `Subsec 

tions' on page

8

.

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.

By default,

dpkg gencontrol

does not include this field in the control file of a binary pack 

age   use the

 is

(or

 isp

) options to achieve this effect.

5.6.6

Priority

This field represents how important that it is that the user have the package installed. See

`Priorities' on page

9

.

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.

By default,

dpkg gencontrol

does not include this field in the control file of a binary pack 

age   use the

 ip

(or

 isp

) options to achieve this effect.

5.6.7

Package

The name of the binary package.

Package names must consist only of lower case letters (

a z

), digits (

0 9

), plus (

+

) and minus

(

) signs, and periods (

.

). They must be at least two characters long and must start with an

alphanumeric character.

5.6.8

Architecture

Depending on context and the control file used, the

Architecture

field can include the fol 

lowing sets of values:

  A unique single word identifying a Debian machine architecture, see `Architecture spec 

ification strings' on page

89

.