On Sat, Jun 30, 2001 at 10:03:37PM -0700, Vineet Kumar wrote: > Incorrect. Using --revision-number=custom.1.0 will result in a > creation of ../kernel-image-2.4.5_custom.1.1_i386.deb . This is a > different revision of the same debian package kernel-image-2.4.5 . He > does want as Joost suggests: --append-to-version=athlon , which will > result in something like > ../kernel-image-2.4.5athlon_Custom.1.00_i386.deb , which is a debian > package for kernel-image-2.4.5athlon , and will insert appropriately > named files in /boot (i.e. vmlinuz-2.4.5athlon , > System.map-2.4.5athlon and config-2.4.5athlon ).
Indeed, so the package name will be "kernel-image-2.4.5-athlon" and the package version will be "Custom.1.00". It will install any modules it contains in /lib/modules/2.4.5-athlon and overwrite any earlier versions of kernel-image-2.4.5-athlon, just like any regular package upgrade. It will not overwrite files in eg. kernel-image-2.4.5 package, if that was already installed. As the manpage explains, --append-to-version simply appends to the EXTRAVERSION makefile variable in the kernel. Already kernel-package recognises it, so if you apply eg. alan cox's patch, you will build a kernel-image-<x.y.z>-ac<n> package automatically. Neat. It is a bit confusing to have an option named --append-to-version, while this option really appends to the name of the package, not its version. Cheers, Joost
