From 7e7f0c97ca15eb48f05c3bf2a52a561e4bad02b2 Mon Sep 17 00:00:00 2001 From: Andres Salomon Date: Mon, 11 Jul 2005 03:22:30 +0000 Subject: [PATCH] whoops. thinko. svn path=/trunk/kernel/source/linux-kernel-2.6.12/; revision=3457 --- debian/templates/control.headers.arch.in | 11 +++++++++++ debian/templates/control.headers.in | 12 ------------ 2 files changed, 11 insertions(+), 12 deletions(-) create mode 100644 debian/templates/control.headers.arch.in diff --git a/debian/templates/control.headers.arch.in b/debian/templates/control.headers.arch.in new file mode 100644 index 000000000..a4641b1fa --- /dev/null +++ b/debian/templates/control.headers.arch.in @@ -0,0 +1,11 @@ +Package: linux-headers-@subarch@@version@-@abiname@-@arch@ +Architecture: @arch@ +Section: devel +Priority: optional +Depends: TODO +Description: Virtual package that depends on all @version@ kernel headers for @arch@ + This package provides common kernel header files for version @version@ on + @arch@, used to build out-of-tree kernel modules and the like. It is mainly + useful for module packages that want to build a module for all flavors of + an architecture, without having to manually list each flavor in its control + file. If you don't know what any of this means, you probably don't need this. diff --git a/debian/templates/control.headers.in b/debian/templates/control.headers.in index dce67d24e..46cc82426 100644 --- a/debian/templates/control.headers.in +++ b/debian/templates/control.headers.in @@ -15,15 +15,3 @@ Description: Common architecture-specific header files for Linux kernel @version apt-get install linux-headers-@version@-@abiname@-$(uname -r) . and it will be unpacked in /usr/src/linux-headers-@version@-@abiname@-(flavour). - -Package: linux-headers-@subarch@@version@-@abiname@-@arch@ -Architecture: @arch@ -Section: devel -Priority: optional -Depends: TODO -Description: Virtual package that depends on all @version@ kernel headers for @arch@ - This package provides common kernel header files for version @version@ on - @arch@, used to build out-of-tree kernel modules and the like. It is mainly - useful for module packages that want to build a module for all flavors of - an architecture, without having to manually list each flavor in its control - file. If you don't know what any of this means, you probably don't need this.