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

purpose of kernel-tree packages



I am wondering what the purpose of the kernel-tree packages is.

First of all, I note the dependency line:

  Package: kernel-tree-2.6.10
  Version: 2.6.10-4
  Depends: kernel-patch-debian-2.6.10 (= 2.6.10-4),
      kernel-source-2.6.10 (= 2.6.10-1) | kernel-source-2.6.10 (= 2.6.10-2)
    | kernel-source-2.6.10 (= 2.6.10-3) | kernel-source-2.6.10 (= 2.6.10-4)

Thus, installing -4 without a 2.6.10 kernel source installed will
pull in the 2.6.10-*1* kernel source.

Second, I note that it depends on the Debian patch and its
description says:

  Its dependencies are structured so that a complete kernel tree
  with Debian patches applied will be available after this package
  is installed.

... but kernel-source packages already have the Debian patch(es)
applied. So why would I need kernel-tree?

  (NB: I note a reference in the description to
  kernel-image-2.6.10-i386, which does not exist)

mrvn suggests that kernel-tree pulls in arch patches on other
arches, but kernel-tree-2.6.9, when inspected in paer's unstable
chroot, does not depend on kernel-patch-2.6.9-hppa.

So I wonder: what is the purpose of the kernel-tree packages? Why do
I need to pull in the Debian kernel-patch (which is only really
needed to *un*apply the patch from kernel source, which is normally
not done, not even by make-kpkg)?

Thanks for any hints.

-- 
Please do not send copies of list mail to me; I read the list!
 
 .''`.     martin f. krafft <madduck@debian.org>
: :'  :    proud Debian developer, admin, user, and author
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!

Attachment: signature.asc
Description: Digital signature


Reply to: