README update: generation of control files.
svn path=/trunk/kernel/source/linux-2.6/; revision=3765
This commit is contained in:
parent
ce663cee1d
commit
ae4cdbeb80
|
@ -43,8 +43,13 @@ Control file
|
|||
------------
|
||||
The master control file debian/control must be generated before
|
||||
the package is uploaded. debian/rules contains the debian/control
|
||||
target, which generates the control file by concatenating the
|
||||
common templates for it and substituting the variables:
|
||||
target, which generates the control file by invoking the
|
||||
debian/bin/gencontrol.py script, which combines the templates from
|
||||
the templates directory and arch/subarch specific defines file to
|
||||
produce the debian/control file. Note that this target is intentionally
|
||||
made to fail with a non-zero exit code to make sure that it is never
|
||||
run during an automatic build. The following variables are substituted
|
||||
into the templates:
|
||||
|
||||
@version@ Upstream kernel version, for example 2.6.11.
|
||||
@major@ The major version, for example 2.6
|
||||
|
@ -69,19 +74,8 @@ common templates for it and substituting the variables:
|
|||
@allheaders@ Given the arch, a list of all the linux-headers packages for the
|
||||
arch - used for kernel-headers-x.y.z-n-arch.
|
||||
|
||||
For each kernel image build the control.source.in template from
|
||||
templates directory is concatenated with the control.in file from the
|
||||
arch/<arch> or arch/<arch>/<subarch> directory, and the following
|
||||
variables are substituted: @version@, @ltver@, @major@, @abiname@.
|
||||
A arch/subarch-specific control.in file should contain only entries
|
||||
for binary linux-image-$(version)-$(abiname)-$(flavour) and
|
||||
flavour-specific linux-headers-$(version)-$(abiname)-$(flavour)
|
||||
packages. linux-headers-$(version)-$(abiname) package entry is
|
||||
included automatically.
|
||||
|
||||
After variable substitution the resulting files are formatted to
|
||||
ensure that the only blank lines are the ones separating the
|
||||
entries (i.e. before the next Package: line).
|
||||
Normally, the arch-specific contents should be controlled by
|
||||
adjusting the corresponding defines file.
|
||||
|
||||
Makefile.inc
|
||||
------------
|
||||
|
|
Loading…
Reference in New Issue