Chapter 5. Control files and their fields
37
5.6.19
Binary
This field is a list of binary packages.
When it appears in the
.dsc
file it is the list of binary packages which a source package can
produce. It does not necessarily produce all of these binary packages for every architecture.
The source control file doesn't contain details of which architectures are appropriate for which
of the binary packages.
When it appears in a
.changes
file it lists the names of the binary packages actually being
uploaded.
The syntax is a list of binary packages separated by commas
10
. Currently the packages must
be separated using only spaces in the
.changes
file.
5.6.20
Installed Size
This field appears in the control files of binary packages, and in the
Packages
files. It gives
the total amount of disk space required to install the named package.
The disk space is represented in kilobytes as a simple decimal number.
5.6.21
Files
This field contains a list of files with information about each one. The exact information and
syntax varies with the context. In all cases the part of the field contents on the same line as the
field name is empty. The remainder of the field is one line per file, each line being indented by
one space and containing a number of sub fields separated by spaces.
In the
.dsc
file, each line contains the MD5 checksum, size and filename of the tar file and (if
applicable) diff file which make up the remainder of the source package
11
. The exact forms of
the filenames are described in `Source packages as archives' on page
117
.
In the
.changes
file this contains one line per file being uploaded. Each line contains the MD5
checksum, size, section and priority and the filename. The section and priority are the values
of the corresponding fields in the main source control file. If no section or priority is specified
then
should be used, though section and priority values must be specified for new packages
to be installed properly.
The special value
byhand
for the section in a
.changes
file indicates that the file in question
is not an ordinary package file and must by installed by hand by the distribution maintainers.
If the section is
byhand
the priority should be
.
If a new Debian revision of a package is being shipped and no new original source archive
is being distributed the
.dsc
must still contain the
Files
field entry for the original source
archive
package
upstream version
.orig.tar.gz
, but the
.changes
file should leave
10
A space after each comma is conventional.
11
That is, the parts which are not the
.dsc
.






footer




 

 

 

 

 Home | About Us | Network | Services | Support | FAQ | Control Panel | Order Online | Sitemap | Contact

gay web hosting

 

Our partners: PHP: Hypertext Preprocessor Best Web Hosting Java Web Hosting Inexpensive Web Hosting  Jsp Web Hosting

Cheapest Web Hosting Jsp Hosting Cheap Hosting

Visionwebhosting.net Business web hosting division of Web Design Plus. All rights reserved