[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Common kernel package technology preview :-)



Hello,

The common kernel package now seems mature enough to be exposed to the public. It may be checked out from svn:

svn://svn.debian.org/svn/kernel/branches/kernel-image-2.6.11

Hopefully, we'll find a more suitable location for it in the near future. To try it out follow those steps:

* Patch the kernel-package :-). It turned out that the kernel-package
  which is currently in sid implements a version check incompatible
  with the way the official kernels are built. I've brought it to
  the maintainer attention and he agreed to fix it. For now you need
  to comment out the line 1172 in /usr/share/kernel-package/rules
  (assuming version 8.135 here):

--- a/kernel/rules      2005-05-07 03:40:22.000000000 -0400
+++ b/kernel/rules      2005-06-02 00:38:06.000000000 -0400
@@ -1169,7 +1169,7 @@
                   fi; )
 ifneq ($(strip $(saved_version)),)
 ifneq ($(strip $(saved_version)),$(strip $(version)))
-HAVE_VERSION_MISMATCH=YES
+#HAVE_VERSION_MISMATCH=YES
 endif
 endif
 endif

  I'll submit a proper patch to BTS and will track this issue.
* Checkout the files from svn.
* Unpack the kernel-source-2.6.11_2.6.11.orig.tar.gz into the top level.
* Symlink checked out directory

  kernel/trunk/kernel/source/kernel-source-2.6.11-2.6.11/debian/patches

  to debian/patches-debian in the common package tree.
* It is now ready to use. debian/rules supports the following
  targets:
  source, tree, doc, patch - to build separate components
  binary-indep             - to build all of the above
  unpack, build, install   - to unpack/build/install the kernel images
  binary-arch              - runs the three above targets
  binary                   - builds everything
* Read the debian/README file and populate your architecture subdirectory
  in debian/arch/$(arch) according to the instructions.
* If you notice any bugs, feel free to correct them :-).

As discussed recently on the list, all packages are now build with linux- prefix, instead of kernel-. As a result, to install them correctly, they require proper Conflicts/Replaces fields which are not in place yet, so it is probable that you will get file conflicts. If you know the right combination of those, feel free to add them.

Another thing: the multi-arch linux-headers package is not there yet. The headers packages are built as before, per architecture, however the scripts directory is now included in them.

Best regards,

Jurij Smakov                                        jurij@wooyd.org
Key: http://www.wooyd.org/pgpkey/                   KeyID: C99E03CC



Reply to: