Allow to specify a custom revision for the generated .deb by
exporting the environment variable KDEB_PKGVERSION.
Signed-off-by: Frans Pop <[email protected]>
---
Hit "send" too early on this one :-(
diff --git a/scripts/package/builddeb b/scripts/package/builddeb
index c9a4dcd..1b8820f 100644
--- a/scripts/package/builddeb
+++ b/scripts/package/builddeb
@@ -14,6 +14,11 @@ set -e
# Some variables and settings used throughout the script
version=$KERNELRELEASE
revision=$(cat .version)
+if [ -n "$KDEB_PKGVERSION" ]; then
+ packageversion=$version-$revision
+else
+ packageversion=$KDEB_PKGVERSION
+fi
tmpdir="$objtree/debian/tmp"
fwdir="$objtree/debian/fwtmp"
packagename=linux-$version
@@ -76,7 +81,7 @@ done
name="Kernel Compiler <$(id -nu)@$(hostname -f)>"
# Generate a simple changelog template
cat <<EOF > debian/changelog
-linux ($version-$revision) unstable; urgency=low
+linux ($packageversion) unstable; urgency=low
* Custom built Linux kernel.
On Wed, 01 Apr 2009, Frans Pop wrote:
> Allow to specify a custom revision for the generated .deb by
> exporting the environment variable KDEB_PKGVERSION.
>
nack
looks like double work circumventling .localversion
On Wednesday 01 April 2009, maximilian attems wrote:
> On Wed, 01 Apr 2009, Frans Pop wrote:
> > Allow to specify a custom revision for the generated .deb by
> > exporting the environment variable KDEB_PKGVERSION.
>
> nack
> looks like double work circumventling .localversion
No. .localversion gets added to the _kernel_ version in the package name.
This is to overrule the standard _package_ version.
I use it for example to automatically create a series of versioned
packages during bisection based on .git/BISECT_LOG:
linux-2.6.29_1_amd64.deb
linux-2.6.29_2_amd64.deb
linux-2.6.29_3_amd64.deb
linux-2.6.29_4_amd64.deb
...
For "normal" packages I use package versions based on 'git describe'.