Commit 86af4a4d authored by Manoj Srivastava's avatar Manoj Srivastava

[master]: Update for the NMU changes.

Signed-off-by: 's avatarManoj Srivastava <srivasta@golden-gryphon.com>
parent 50b62d70
......@@ -112,7 +112,7 @@ install: genpo4a
$(install_file) kernel-package.5 $(MAN5DIR)/kernel-package.5
$(install_file) make-kpkg.8 $(MAN1DIR)/make-kpkg.1
$(install_file) kernel-packageconfig.8 $(MAN8DIR)/
for lang in fr; do \
for lang in de fr; do \
test ! -f kernel-pkg.conf.$$lang.5 || test -d $(MANTOP)/$$lang/man5 || \
mkdir -p $(MANTOP)/$$lang/man5; \
test ! -f kernel-pkg.conf.$$lang.5 || \
......@@ -158,15 +158,15 @@ install: genpo4a
chmod 0755 $(prefix)/usr/share/$(package)/rules
clean distclean:
for lang in es fr; do \
for lang in de fr; do \
test ! -f kernel-pkg.conf.$$lang.5 || \
rm kernel-pkg.conf.$$lang.5 ; \
test ! -f kernel-img.conf.$$lang.5 || \
rm kernel-img.conf.$$lang.5 ; \
test ! -f kernel-package.$$lang.5 || \
rm kernel-package.$$lang.5 ; \
test ! -f make-kpkg.$$lang.5 || \
test ! -f make-kpkg.$$lang.8 || \
rm make-kpkg.$$lang.8 ; \
test ! -f kernel-packageconfig.$$lang.5 || \
test ! -f kernel-packageconfig.$$lang.8 || \
rm kernel-packageconfig.$$lang.8 ; \
done
......@@ -62,13 +62,13 @@ Phase TWO: Create a portable kernel image .deb file
Or just rm -rf ./debian, if you do not want to get rid of the
previous state and only rebuild whatever required for any
changes.
4% $Get_Root make-kpkg --revision=custom.1.0 kernel_image
4% $Get_Root make-kpkg --revision=1.0.custom kernel_image
(Get_Root is whatever you need to become root -- fakeroot or
sudo are examples that come to mind). NOTE: if you have
instructed your boot loader to expect initrd kernels (which is
the norm for recent kernel image packages) you need to
add --initrd to the line above.
% $Get_Root make-kpkg --initrd --revision=custom.1.0 kernel_image
% $Get_Root make-kpkg --initrd --revision=1.0.custom kernel_image
Personally, I prefer non initrd images for my personal machines,
since then adding third party modules to the machine has fewer
gotchas. Note that you will have to arrange for the actual
......@@ -235,13 +235,13 @@ differences in builds. It then looks like:
I've found that using a two-level scheme where the major level starts
with a letter nicely does the job -- unless epochs are used,
(--revision custom.Y, so the image package become
kernel-image-X.X.XX-custom.Y.deb), and dselect and dpkg -BOGiE will
(--revision Y.custom, so the image package become
kernel-image-X.X.XX-Y.custom.deb), and dselect and dpkg -BOGiE will
refuse to downgrade to a generic kernel (don't give the BOG arguments
to dpkg if you actually do want to downgrade later).
The reason for telling kernel-package that the package has a version
"custom-x.y.whatever.you-want.to+add.more-just.do.not+use.an=underscore"
"x.y.whatever.you-want.to+add.more-just.do.not+use.an=underscore"
is that to dpkg that is always a higher version number than any version
number starting with a numeral ( e.g. "a" > "2" like "b" > "a". ) This way,
dselect will not try to upgrade your "roll-it-yourself" kernel-image when
......@@ -251,8 +251,8 @@ a new build of the distribution default kernel appears in the archive.
Unfortunately, this fails if the upstream maintainer uses epochs to
correct a version misnumbering ;-(. The good news is that you can add
your own epoch to your customized image, ugly though that may
be. (--revision 1:custom.Y; the kernel image file shall remain
kernel-image-X.X.XX-custom.Y.deb, but dpkg shall know that it should
be. (--revision 1:Y.custom; the kernel image file shall remain
kernel-image-X.X.XX-Y.custom.deb, but dpkg shall know that it should
not replace that with a standard kernel with an epoch. Hopefully, we
shall never see an epoch greater than 1 on a standard kernel, but who
knows. Choose your epoch, if you must use it, wisely. I fear, though,
......@@ -264,7 +264,7 @@ So, try using an epoch for your custom packages:
make-kpkg clean
(or just rm -rf ./debian, if you do not want to rebuild from the
beginning)
$Get_Root make-kpkg --revision=3:custom.1.0 kernel_image
$Get_Root make-kpkg --revision=3:1.0.custom kernel_image
(Get_Root is whatever you need to become root -- fakeroot or
sudo are examples that come to mind).
......@@ -273,7 +273,7 @@ sound card or you discovered that you suddenly want masquerading in your
kernel enabled, you'll type:
make-kpkg clean
(or just rm -rf ./debian)
$Get_Root make-kpkg --revision=3:custom.2.0 kernel_image
$Get_Root make-kpkg --revision=3:2.0.custom kernel_image
(Get_Root is whatever you need to become root -- fakeroot or
sudo are examples that come to mind).
(remember to do rm -rf ./debian or a make-kpkg clean before you
......@@ -304,7 +304,7 @@ called. You can thuse select your own; initramfs-tools or yaird
make-kpkg clean
(or just rm -rf ./debian, if you do not want to rebuild from the
beginning)
$Get_Root make-kpkg --initrd --revision=3:custom.2.0 kernel_image
$Get_Root make-kpkg --initrd --revision=3:2.0.custom kernel_image
With the new kernel-package conventions, you also need the example
scripts in /etc/kernel/postinst.d/ and /etc/kernel/postrm.d, to create
......@@ -368,9 +368,9 @@ around, you might be interested in:
When make-kpkg is finished, you'll have
kernel-image-2.0.29_custom.1.0_i386.deb and all it takes now is to
kernel-image-2.0.29_1.0.custom_i386.deb and all it takes now is to
install the package (as root):
# dpkg -i kernel-image-2.0.29_custom.1.0_i386.deb
# dpkg -i kernel-image-2.0.29_1.0.custom_i386.deb
This will install the kernel, the modules, the map file and do some other
administrativia and finally it will ask you if you want to make a
......@@ -388,7 +388,7 @@ Unfortunately, there is no reasonable solution; I suggest moving the
old modules directory before installation, like so (need to be root):
# mv /lib/modules/2.0.29 /lib/modules/2.0.29.save
# dpkg -i kernel-image-2.0.29_custom.1.0_i386.deb
# dpkg -i kernel-image-2.0.29_1.0.custom_i386.deb
and later get rid of the .save directory.
People who want to have multiple flavors of the same kernel version
......@@ -550,10 +550,10 @@ Please see kernel-img.conf (5).
To generate a new kernel image, just run
% make-kpkg clean
(or just rm -rf ./debian)
% $Get_Root make-kpkg --revision=custom.1.0 kernel_image
% $Get_Root make-kpkg --revision=1.0.custom kernel_image
(Get_Root is whatever you need to become root -- fakeroot or
sudo are examples that come to mind) or (if you use initrd)
$Get_Root make-kpkg --initrd --revision=3:custom.2.0 kernel_image
$Get_Root make-kpkg --initrd --revision=3:2.0.custom kernel_image
This will create a default kernel image (as in the image package or
available on the boot disks. The kernel image package produced, on
......@@ -577,10 +577,10 @@ have a .config file, just copy it to this directory, and you are go.
With a custom .config file in place (created as above) run again:
% make-kpkg clean
(or just rm -rf ./debian)
% $Get_Root make-kpkg --revision=custom.1.0 kernel_image
% $Get_Root make-kpkg --revision=1.0.custom kernel_image
(Get_Root is whatever you need to become root -- fakeroot or
sudo are examples that come to mind).
$Get_Root make-kpkg --initrd --revision=3:custom.2.0 kernel_image
$Get_Root make-kpkg --initrd --revision=3:2.0.custom kernel_image
|-----------------------------------------------------------------------|
| Special needs |
......@@ -588,8 +588,8 @@ With a custom .config file in place (created as above) run again:
| whatever reasons that maybe -- I think that the separate step as |
| non-fake-root is not required, but that is a personal opinion) |
| % test ! -d debian || rm -rf debian |
| % make-kpkg --revision=custom.1.0 build |
| % $Get_Root make-kpkg --revision=custom.1.0 kernel_image |
| % make-kpkg --revision=1.0.custom build |
| % $Get_Root make-kpkg --revision=1.0.custom kernel_image |
| (Get_Root is whatever you need to become root -- fakeroot or |
| sudo are examples that come to mind) |
| |
......@@ -605,24 +605,24 @@ With a custom .config file in place (created as above) run again:
| If you use initrd images (and have told your boot loader so) you need |
| to include the --initrd option on the command line, like so |
| |
| % $Get_Root make-kpkg --initrd --revision=3:custom.2.0 kernel_image |
| % $Get_Root make-kpkg --initrd --revision=3:2.0.custom kernel_image |
| |
-------------------------------------------------------------------------
To create a source or header package, run
% make-kpkg clean
(or rm -rf ./debian)
% $Get_Root make-kpkg --revision=custom.1.0 kernel_source
% $Get_Root make-kpkg --revision=custom.1.0 kernel_headers
% $Get_Root make-kpkg --revision=1.0.custom kernel_source
% $Get_Root make-kpkg --revision=1.0.custom kernel_headers
Note: You only need one of these.
(Get_Root is whatever you need to become root -- fakeroot or
sudo are examples that come to mind).
Similarly, the documentation package is built by:
% $Get_Root make-kpkg --revision=custom.1.0 kernel_doc
% $Get_Root make-kpkg --revision=1.0.custom kernel_doc
Or if you want to generate the whole package,
% $Get_Root make-kpkg --revision=custom.1.0 \
% $Get_Root make-kpkg --revision=1.0.custom \
--pgpsign="Your pgp ID" buildpackage
Note that this needs a pgp key.
(Get_Root is whatever you need to become root -- fakeroot or
......@@ -965,7 +965,7 @@ next kernel compilation, but you have not yet compiled it.
make-kpkg clean
(or just rm -rf ./debian)
make-kpkg -rootcmd fakeroot --append-to-version -custom.${VER} \
--revision custom.${VER} kernel_image modules-image
--revision ${VER}.custom kernel_image modules-image
This one also builds any stand-alone modules packages you may have
installed on your machine.
......
debian @ f1c40a0e
Subproject commit b7235618266184db87ab09348d6ad0644495c55c
Subproject commit f1c40a0e216950b985f29102e32159548808dd81
......@@ -38,11 +38,15 @@ process to allow local options for handling some aspects of the
installation, overriding the defaults built into the image itself.
.PP
The format of the file is a simple
.B VAR = VALUE
.IB VAR = VALUE
pair. Boolean values may be specified as
.I Yes, True, 1,
.IR Yes ,
.IR True ,
.IR 1 ,
and
.I No, False, 0,
.IR No ,
.IR False ,
.IR 0 ,
and are case insensitive.
This file is automatically created by the installation script in
certain circumstances.
......@@ -50,7 +54,7 @@ certain circumstances.
At the moment, the user modifiable variables supported are:
.TP
.B postinst_hook
.BR DEPRECATED:
.BR DEPRECATED :
Set this variable to a script to be executed during installation. The
path can be a relative path if the script lives in a safe path -- that
is, if it lives in /bin, /sbin, /usr/bin, or /usr/sbin, or must be an
......@@ -70,8 +74,8 @@ of the kernel image itself. Errors in the script shall cause the
postinst to fail. Since debconf is in use before the script is called,
this script should issue no diagnostic messages to stdout -- while the
postinst does call
.B db_stop
, debconf does not restore stdout, so messages to stdout disappear.
.BR db_stop ,
debconf does not restore stdout, so messages to stdout disappear.
An example script for grub users is present in
/usr/share/doc/kernel\-package/ directory.
This script is run
......@@ -79,7 +83,7 @@ This script is run
the scripts in /etc/kernel/postinst.d directory.
.TP
.B postrm_hook
.BR DEPRECATED:
.BR DEPRECATED :
Set this variable to a script to be executed in the postrm (that is,
after the image has been removed) after all the remove actions have
been performed. The path can be a relative path if the script lives in
......@@ -97,14 +101,14 @@ of the kernel image itself. Errors in the script shall produce a
warning message, but shall be otherwise ignored. Since debconf is in
use before the script is called, this script should issue no
diagnostic messages to stdout -- while the postinst does call
.B db_stop
, debconf does not restore stdout, so messages to stdout disappear.
.BR db_stop ,
debconf does not restore stdout, so messages to stdout disappear.
This script is run
.I after
the scripts in /etc/kernel/postrm.d directory.
.TP
.B preinst_hook
.BR DEPRECATED:
.BR DEPRECATED :
Set this variable to a script to be executed before the package is
unpacked, and can be used to put in additional checks. The path can be
a relative path if the script lives in a safe path -- that is, if it
......@@ -123,7 +127,7 @@ This script is run
the scripts in /etc/kernel/preinst.d directory.
.TP
.B prerm_hook
.BR DEPRECATED:
.BR DEPRECATED :
Set this variable to a script to be executed before the package files
are removed (so any added files may be removed) . The path can be a
relative path if the script lives in a safe path -- that is, if it
......@@ -140,14 +144,14 @@ of the kernel image itself. Errors in the script shall cause the prerm
to fail. Since debconf is in use before the script is called, this
script should issue no diagnostic messages to stdout -- while the
postinst does call
.B db_stop
, debconf does not restore stdout, so messages to stdout disappear.
.BR db_stop ,
debconf does not restore stdout, so messages to stdout disappear.
This script is run
.I after
the scripts in /etc/kernel/prerm.d directory.
.TP
.B src_postinst_hook
.BR DEPRECATED:
.BR DEPRECATED :
Unlike the other hook variables, this is meant for a script run during
the post inst of a docs, headers or a source package. Using this hook
for the headers package is now being deprecated, at some point the
......@@ -170,7 +174,7 @@ This script is run
the scripts in /etc/kernel/src_postinst.d directory.
.TP
.B header_postinst_hook
.BR DEPRECATED:
.BR DEPRECATED :
Unlike the other hook variables, this is meant for a script run during
the post inst of a headers package only. The path can be a relative
path if the script lives in a safe path -- that is, if it lives in
......@@ -227,7 +231,7 @@ is to relink (delete) the source link (YES).
.B silent_modules
This option has been put in for the people who are vastly irritated on
being warned about preexisting modules directory
.I /lib/modules/$version
.IR /lib/modules/$version .
That directory may belong to an old or defunct kernel image package,
in which case problems may arise with leftover modules in that
directory tree, or the directory may legitimately exist due to a
......@@ -236,7 +240,7 @@ that has already been unpacked. In this latter case the existence of
the directory is benign. If you set this variable, you shall no
longer be given a chance to abort if a preexisting modules directory
.I /lib/modules/$version
is detected. This is unset be default.
is detected. This is unset by default.
.TP
.B ignore_depmod_err
If set, does not prompt to continue after a depmod problem in the
......@@ -245,12 +249,12 @@ mask a problem with the kernel image. A diagnostic is still
issued. This is unset be default.
.SH FILES
The file described here is
.I /etc/kernel\-img.conf.
.IR /etc/kernel\-img.conf .
.SH "SEE ALSO"
.BR make (1),
.BR make\-kpkg (1),
.BR kernel\-pkg.conf (5),
.BR make (1),
.B The GNU Make manual.
.B The GNU Make manual
.SH BUGS
There are no bugs. Any resemblance thereof is delirium. Really.
.SH AUTHOR
......
......@@ -27,18 +27,18 @@
.\" NAME should be all caps, SECTION should be 1-8, maybe w/ subsection
.\" other parms are allowed: see man(7), man(1)
.SH NAME
kernel\-package \- A system for creating kernel related packages
kernel\-package \- system for creating kernel related packages
.SH "DESCRIPTION"
The
.B kernel\-package
package grew out of desire to automate the routine steps required to
compile and install a custom kernel. If you are looking for
instructions on how to use
.B kernel\-package,
.BR kernel\-package ,
please have a look at the manual
.B make\-kpkg (1).
.BR make\-kpkg (1).
Configuring instructions are to be found in
.B kernel\-pkg.conf(5).
.BR kernel\-pkg.conf (5).
.SH "Advantages of using kernel\-package"
.RS
.TP
......@@ -60,7 +60,7 @@ It has a facility for you to keep multiple flavors of the
same kernel version on your machine (you could have a stable
2.0.36 version, and a 2.0.36 version patched with the latest
drivers, and not worry about contaminating the modules in
.I /lib/modules).
.IR /lib/modules ).
.TP
.B iv) Built in defaults
It knows that some architectures do not have vmlinuz (using
......@@ -85,7 +85,7 @@ depend on the kernel packages.
.B vii) Configuration tracking
It keeps track of the configuration file for each kernel image
in
.I /boot,
.IR /boot ,
which is part of the image package, and hence is the kernel image and
the configuration file are always together.
.TP
......@@ -123,7 +123,7 @@ this can allow, amongst other things, grub users to add and remove
kernel image stanzas from the grub menu (example scripts to do this
are in the package). There are directories under
.I /etc/kernel
where related package may drop off scripts that will be run by the
where related packages may drop off scripts that will be run by the
maintainer scripts of the packages created by kernel package. Before
running these scripts, the environment variable
.B KERNEL_PACKAGE_VERSION
......@@ -156,15 +156,17 @@ or
.B super
or be root to create a kernel image .deb file (this is not as bad as
it used to be before
.B fakeroot)
.BR fakeroot ).
.RE
.SH FILES
.I /etc/kernel\-pkg.conf.
.I /etc/kernel\-img.conf.
.TP
.I /etc/kernel\-pkg.conf
.TP
.I /etc/kernel\-img.conf
.SH "SEE ALSO"
.BR make\-kpkg (1),
.BR make (1),
.B The GNU Make manual.
.BR make\-kpkg (1),
.B The GNU Make manual
.SH BUGS
There are no bugs. Any resemblance thereof is delirium. Really.
.SH AUTHOR
......
......@@ -26,7 +26,7 @@
.\"
.TH KERNEL\-PACKAGECONFIG 8 "Jan 7 1997" "Debian" "Debian GNU/Linux manual"
.SH NAME
kernel\-packageconfig \- Internal handler of /etc/kernel\-pkg.conf.
kernel\-packageconfig \- internal handler of /etc/kernel\-pkg.conf
.SH SYNOPSIS
.B kernel\-packageconfig
.SH DESCRIPTION
......@@ -42,10 +42,10 @@ meant for general use.
.SH OPTIONS
This utility does not have any options.
.SH FILES
The files affected by this program are
.I /etc/kernel\-pkg.conf.
The file affected by this program is
.IR /etc/kernel\-pkg.conf .
.SH "SEE ALSO"
.B kernel\-pkg.conf (5)
.BR kernel\-pkg.conf (5)
.SH AUTHOR
This manual page was written by Manoj Srivastava <srivasta@debian.org>,
for the Debian GNU/Linux system.
......
......@@ -44,31 +44,31 @@ you may put any legal Makefile directive in that file (just make very
sure you know what you are doing). If the per user configuration file
.I ~/.kernel\-pkg.conf
exists, it is loaded in favor of the system wide configuration file
.I /etc/kernel\-pkg.conf.
.IR /etc/kernel\-pkg.conf .
.PP
All the variables have reasonable default values, and maybe
overridden on a per run or a per individual basis by using
environment variables. Some of the variables can further be
overridden by options to
.B make\-kpkg.
.BR make\-kpkg .
.PP
At the moment, the user modifiable variables supported are:
.TP
.B maintainer
Local kernel (image, header, doc, etc) package maintainer. Set up at
Local kernel (image, header, doc, etc.) package maintainer. Set up at
package installation by the
.IR postinst.
.IR postinst .
Can be overridden by the environment variable
.B KPKG_MAINTAINER.
.BR KPKG_MAINTAINER .
Please note that any apostrophes "'" shall have to be quoted like so:
maintainer = John O'\\''Brien. Yes, this is ugly, but this works.
.TP
.B email
The email address of that person. Set up at package installation by
the
.IR postinst.
.IR postinst .
Can be overridden by the environment variable
.B KPKG_EMAIL.
.BR KPKG_EMAIL .
.TP
.B pgp
A key-ID to use when signing packages. Usually passed along to
......@@ -77,28 +77,28 @@ using the
.I \-k
option, and also third party modules in the
.B KMAINT
environment variable, if separate modules (like pcmcia etc) are being
environment variable, if separate modules (like pcmcia, etc.) are being
built in
.IR $MODULE_PATH.
.IR $MODULE_PATH .
Can be overridden by the environment variable
.B PGP_SIGNATURE,
.BR PGP_SIGNATURE ,
and is overridden (again) by the
.IR \-\-pgpsign
option of
.B make\-kpkg.
.BR make\-kpkg .
Defaults to
.I maintainer.
.IR maintainer .
(Optional)
.TP
.B debian
The version of the kernel packages, includes both the upstream version
and the Debian revision. Can be overridden
by the environment variable
.B DEBIAN_REVISION,
.BR DEBIAN_REVISION ,
and is overridden (again) by the
.IR \-\-revision
option of
.B make\-kpkg.
.BR make\-kpkg .
Defaults to
.I <VERSION>-10.0.0.Custom
(Optional)
......@@ -106,22 +106,22 @@ Defaults to
.B debian_revision_mandatory
Normally unset. If this, or the environment variable
.B DEBIAN_REVISION_MANDATORY
are set, then not providing a debian revision results in an error (and
are set, then not providing a Debian revision results in an error (and
.B make\-kpkg
shall not provide a default value of 10.0.0.Custom)
.TP
.B kimage
The kernel image type (i.e. zImage or bzImage). Can be
overridden from the environment variable
.B IMAGE_TYPE,
.BR IMAGE_TYPE ,
and is overridden (again) by the options
.IR \-\-zimage
or
.IR \-\-bzimage
of
.B make\-kpkg.
.BR make\-kpkg .
Defaults to
.I bzImage.
.IR bzImage .
(Optional)
.TP
.B config_target
......@@ -150,9 +150,9 @@ This should be set to a means of gaining superuser access (for
example,
.I `sudo'
or
.I `fakeroot')
.IR `fakeroot' )
as needed by
.B dpkg\-buildpackages'
.BR dpkg\-buildpackages '
\-r option. The environment variable
.B ROOT_CMD
overrides this. Use the environment variable
......@@ -194,18 +194,18 @@ from the top level of the (temporary) kernel image tree before the
kernel image is packaged. This has no effect on anything other than
the image that is being packaged -- if the script operates on the
current directory and its children, the original source tree should
remain intact. This is to facilitate massaging of the kernel image
remain intact. This is to facilitate messaging of the kernel image
that is packaged.
.TP
.B source_clean_hook
Set to point to an executable, this shall cause that executable to run
from the top level of the (temporary) kernel source tree before the
sources are packaged,
.I ./debian/tmp\-source/usr/src/kernel\-source\-X.X.XX.
.IR ./debian/tmp\-source/usr/src/kernel\-source\-X.X.XX .
This has no effect on anything other than the sources that are being
packaged -- if the script operates on the current directory and its
children, the original source tree should remain intact. This is to
facilitate massaging of the kernel sources that are packaged (for
facilitate messaging of the kernel sources that are packaged (for
example, to remove version control directories, or to prune away
unwanted architectures).
.TP
......@@ -215,7 +215,7 @@ from the top level of the kernel headers before the headers are
packaged. This has no effect on anything other than the sources that
are being packaged -- if the script operates on the current directory
and its children, the original source tree should remain intact. This
is to facilitate massaging of the kernel headers that are packaged
is to facilitate messaging of the kernel headers that are packaged
(for example, to remove version control directories, or to prune away
unwanted architectures).
.TP
......@@ -225,7 +225,7 @@ from the top of the documentation tree before kernel documentation is
packaged. This has no effect on anything other than the documentation
that is being packaged -- if the script operates on the current
directory and its children, the original source tree should remain
intact. This is to facilitate massaging of the kernel documentation
intact. This is to facilitate messaging of the kernel documentation
that is packaged (for example, to remove version control directories,
or to prune away unwanted architectures).
.TP
......@@ -255,7 +255,7 @@ overrides this. The default is unset.
This is meant to be used by the
.I libc6
maintainer, when he compiles
.I libc6,
.IR libc6 ,
to also package up the corresponding headers.
.B DO NOT SET THIS
unless you know what you are doing, since a mismatch between the
......@@ -306,7 +306,7 @@ set this variable to the dir where you want the image. This may be of
help to
.B loadlin
users. Defaults to
.I /boot.
.IR /boot .
.TP
.B MODULE_LOC
Set this variable, either in the environment or in the config file, to
......@@ -321,7 +321,7 @@ Defaults exist in the rules file. These are the values used if no
customization is done.
.IP b)
Variables can be set in the config file
.I /etc/kernel\-pkg.conf.
.IR /etc/kernel\-pkg.conf .
These values override the defaults.
.IP c)
Variables can also be set by setting a corresponding environment
......@@ -337,14 +337,14 @@ command line
This overrides all the above methods.
.SH FILES
The file described here is
.I /etc/kernel\-pkg.conf.
.I /etc/kernel\-pkg.conf
or
.I ~/.kernel\-pkg.conf.
.IR ~/.kernel\-pkg.conf .
.SH "SEE ALSO"
.BR make (1),
.BR make\-kpkg (1),
.BR kernel\-img.conf (5),
.BR make (1),
.B The GNU Make manual.
.B The GNU Make manual
.SH BUGS
There are no bugs. Any resemblance thereof is delirium. Really.
.SH AUTHOR
......
CONFIG_PACKET=y
# CONFIG_CIFS_EXPERIMENTAL is not set
CONFIG_SLIP_SMART=y
CONFIG_SUNRPC_GSS=m
# CONFIG_NFSD_V4 is not set
# CONFIG_SMB_NLS_DEFAULT is not set
# CONFIG_CODA_FS_OLD_API is not set
CONFIG_CIFS_STATS=y
CONFIG_CIFS_XATTR=y
# CONFIG_SLIP_MODE_SLIP6 is not set
CONFIG_SLIP_COMPRESSED=y
CONFIG_ECONET_AUNUDP=y
CONFIG_RXRPC=m
# CONFIG_CIFS_POSIX is not set
CONFIG_ECONET_NATIVE=y
CONFIG_EQUALIZER=m
CONFIG_NET_CLS_ROUTE=y
CONFIG_PACKET_MMAP=y
CONFIG_AEABI=y
CONFIG_VFP=y
......@@ -30,7 +30,7 @@ Priority: optional
Provides: =ST-source, =ST-source-=CV
Depends: binutils, bzip2, file
Recommends: libc6-dev | libc-dev, gcc | c-compiler, make (>= 3.80-10), po-debconf, gettext, binutils (>= 2.12), util-linux (>= 2.10o), module-init-tools (>= 0.9.10), debianutils (>= 2.30)
Suggests: libncurses-dev | ncurses-dev, kernel-package, xmlto, libdb3-dev, libncurses-dev, docbook-utils, e2fsprogs (>= 1.29), linux-initramfs-tool, ksymoops
Suggests: libncurses-dev | ncurses-dev, kernel-package, xmlto, libdb3-dev, libncurses-dev, docbook-utils, e2fsprogs (>= 1.29), linux-initramfs-tool
Description: Linux kernel source for version =V
This package provides the source code for the Linux kernel, specifically,
version =V.
......
......@@ -47,7 +47,7 @@ ifeq ($(strip $(architecture)),arm)
NEED_DIRECT_GZIP_IMAGE=NO
kimagesrc = arch/$(KERNEL_ARCH)/boot/zImage
kimagedest = $(INT_IMAGE_DESTDIR)/vmlinuz-$(KERNELRELEASE)
DEBCONFIG = $(CONFDIR)/config.arm
DEBCONFIG = $(CONFDIR)/config.$(DEB_HOST_ARCH)
endif
kelfimagesrc = vmlinux
kelfimagedest = $(INT_IMAGE_DESTDIR)/vmlinux-$(KERNELRELEASE)
......
......@@ -30,18 +30,6 @@
##
###############################################################################
# make it possible to build s390x kernels on s390 for 2.4 kernels only
# because 2.6 always use s390 as architecture.
ifeq (4,$(PATCHLEVEL))
ifeq (,$(findstring $(KPKG_SUBARCH),s390 s390x))
KPKG_SUBARCH = s390
endif
KERNEL_ARCH = $(KPKG_SUBARCH)
ifneq ($(shell uname -m),$(KPKG_SUBARCH))
UNAME_MACHINE = $(KPKG_SUBARCH)
export UNAME_MACHINE
endif
endif
kimage := vmlinuz
target = image
NEED_DIRECT_GZIP_IMAGE=NO
......
......@@ -59,9 +59,6 @@ endif
ifeq ($(strip $(architecture)),armeb)
include $(DEBDIR)/ruleset/arches/armeb.mk
endif
ifeq ($(strip $(architecture)),armel)
include $(DEBDIR)/ruleset/arches/armel.mk
endif
##### PowerPC and PowerPC architecture
ifneq ($(strip $(filter ppc powerpc ppc64 powerpc64,$(architecture))),)
......
common @ d63051be
Subproject commit 5c6f314d97163600d33f2725c1a26d9cec9f0615
Subproject commit d63051bedad935bb9d65c2e6b76996e2ae3cc71a
......@@ -124,7 +124,7 @@ endif
ifndef CROSS_COMPILE
ifeq ($(strip $(MAKING_VIRTUAL_IMAGE)),)
ifneq ($(strip $(architecture)),$(strip $(DEB_BUILD_ARCH)))
ifneq ($(strip $(architecture)),$(strip $(word 1,$(DEB_BUILD_ARCH_CPU) $(DEB_BUILD_GNU_CPU))))
#KERNEL_CROSS:=$(architecture)-$(strip $(DEB_HOST_ARCH_OS))-
KERNEL_CROSS:=$(DEB_HOST_GNU_TYPE)-
ifeq ($(architecture), amd64)
......
......@@ -52,9 +52,6 @@ ifneq (,$(filter %-64,$(KPKG_SUBARCH)))
KERNEL_ARCH = mips64
endif
ifeq ($(strip $(architecture)),armel)
KERNEL_ARCH := arm
endif
ifeq ($(strip $(architecture)),armeb)
KERNEL_ARCH := arm
endif
......
......@@ -64,6 +64,8 @@ USE_KBUILD=$(shell if [ $(VERSION) -lt 2 ]; then \
echo "YES"; \
fi)
LGUEST_SUBDIR = $(word 1,$(wildcard Documentation/lguest Documentation/virtual/lguest tools/lguest))
define save_upstream_debianization
@echo save_upstream_debianization
test ! -e scripts/package/builddeb || mv -f scripts/package/builddeb scripts/package/builddeb.kpkg-dist
......@@ -323,8 +325,11 @@ ifeq ($(DEB_HOST_ARCH_OS), linux)
endif
endif
ifneq ($(strip $(shell grep -E ^[^\#]*CONFIG_LGUEST $(CONFIG_FILE))),)
ifeq ($(LGUEST_SUBDIR),)
$(error Cannot find lguest tools)
endif
$(MAKE) $(do_parallel) $(EXTRAV_ARG) $(FLAV_ARG) ARCH=$(KERNEL_ARCH) \
$(CROSS_ARG) -C Documentation/lguest
$(CROSS_ARG) -C $(LGUEST_SUBDIR)
endif
else
ifeq ($(DEB_HOST_ARCH_OS), kfreebsd)
......@@ -358,9 +363,10 @@ real_stamp_clean:
ifeq ($(strip $(DEB_HOST_ARCH_OS)), linux)
$(save_upstream_debianization)
test ! -f .config || cp -pf .config ,,precious
test ! -d Documentation/lguest || \
$(MAKE) $(FLAV_ARG) $(EXTRAV_ARG) $(CROSS_ARG) \
ARCH=$(KERNEL_ARCH) -C Documentation/lguest clean
ifneq ($(LGUEST_SUBDIR),)
$(MAKE) $(FLAV_ARG) $(EXTRAV_ARG) $(CROSS_ARG) \
ARCH=$(KERNEL_ARCH) -C $(LGUEST_SUBDIR) clean
endif
test ! -f Makefile || \
$(MAKE) $(FLAV_ARG) $(EXTRAV_ARG) $(CROSS_ARG) \
ARCH=$(KERNEL_ARCH) distclean
......
......@@ -58,7 +58,9 @@ ifneq ($(strip $(shell if [ -x /usr/bin/db2html ]; then echo YSE; fi)),)
$(MAKE) mandocs htmldocs
endif
-tar cf - Documentation | (cd $(DOCDIR); umask 000; tar xsf -)
rm -f $(DOCDIR)/Documentation/lguest/lguest $(DOCDIR)/Documentation/lguest/lguest.lds
ifneq ($(LGUEST_SUBDIR),)
rm -f $(DOCDIR)/$(LGUEST_SUBDIR)/lguest $(DOCDIR)/$(LGUEST_SUBDIR)/lguest.lds
endif
test ! -d $(DOCDIR)/Documentation/DocBook || \
rm -f $(DOCDIR)/Documentation/DocBook/Makefile \
$(DOCDIR)/Documentation/DocBook/*.sgml \
......@@ -75,15 +77,12 @@ endif
######################################################################
####
######################################################################
ifneq ($(shell if [ $(VERSION) -ge 2 ] && [ $(PATCHLEVEL) -ge 5 ]; then \
echo new;fi),)
find -name Kconfig -print0 | xargs -0r cat | \
(umask 000 ; cat > $(DOCDIR)/Kconfig.collected)
# removing if empty should be faster than running find twice
if ! test -s $(DOCDIR)/Kconfig.collected ; then \
rm -f $(DOCDIR)/Kconfig.collected ; \
fi
endif
ifneq ($(strip $(doc_clean_hook)),)
(cd $(DOCDIR); \
test -x $(doc_clean_hook) && $(doc_clean_hook))
......
......@@ -31,9 +31,7 @@
###############################################################################
LINK_ARCH=$(KERNEL_ARCH)
ifeq ($(shell if [ $(PATCHLEVEL) -eq 6 ] && [ $(SUBLEVEL) -gt 23 ] ; then \
if [ $(KERNEL_ARCH) = "i386" ] || [ $(KERNEL_ARCH) = "x86_64" ] ; then \
echo "yes" ; fi ; fi ),yes)
ifneq ($(filter i386 x86_64,$(KERNEL_ARCH)),)
LINK_ARCH=x86