summaryrefslogtreecommitdiffstats
path: root/scripts/package/buildtar
diff options
context:
space:
mode:
authorBorislav Petkov <bp@suse.de>2013-03-06 09:05:47 +0100
committerMichal Marek <mmarek@suse.cz>2013-04-08 16:04:28 +0200
commit6bc6c9409de03987736df58c411c3aa7b5aed051 (patch)
treec43f617a982ee4092430194ffaccdcb1ab6cd3f0 /scripts/package/buildtar
parentbad6a4092e7f87c5310ff342bc0d766a44bcf8fa (diff)
downloadlinux-6bc6c9409de03987736df58c411c3aa7b5aed051.tar.bz2
buildtar: Add ARCH to the archive name
When dealing with multiple sub-arches (like 32- and 64-bit on x86, for example) generating a bunch of kernel tar archives with the same name but for different sub-arches could get confusing and error-prone. Also, the build process could overwrite otherwise unrelated builds and you probably don't want that. So, add the architecture to the archive name for more clarity and less shoot-yourself-in-the-foot practices. Signed-off-by: Borislav Petkov <bp@suse.de> Signed-off-by: Michal Marek <mmarek@suse.cz>
Diffstat (limited to 'scripts/package/buildtar')
-rw-r--r--scripts/package/buildtar2
1 files changed, 1 insertions, 1 deletions
diff --git a/scripts/package/buildtar b/scripts/package/buildtar
index 62d8234f8787..cdd9bb909bcd 100644
--- a/scripts/package/buildtar
+++ b/scripts/package/buildtar
@@ -16,7 +16,7 @@ set -e
# Some variables and settings used throughout the script
#
tmpdir="${objtree}/tar-install"
-tarball="${objtree}/linux-${KERNELRELEASE}.tar"
+tarball="${objtree}/linux-${KERNELRELEASE}-${ARCH}.tar"
#