From: Zdenek Kaspar <zkaspar82@gmail.com>
To: linux-kbuild@vger.kernel.org
Subject: Add make tarxz-pkg build option
Date: Fri, 28 Jan 2011 23:21:46 +0100 [thread overview]
Message-ID: <4D43417A.1020603@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 234 bytes --]
Hi! Most distributions use xz-utils already, is it possible to add
tarxz-pkg option ?
NB: If someone thinks xz -9 is a bit hardcore, it's not much different
like when bzip2 -9 was introduced into buildtar as an option imo..
TIA, Z.
[-- Attachment #2: add-tarxz-target.diff --]
[-- Type: text/plain, Size: 1174 bytes --]
Signed-off-by: Zdenek Kaspar <zkaspar82@gmail.com>
--- a/scripts/package/Makefile 2011-01-28 23:05:03.000000000 +0100
+++ b/scripts/package/Makefile 2011-01-28 23:07:10.000000000 +0100
@@ -142,7 +142,9 @@
@echo ' tar-pkg - Build the kernel as an uncompressed tarball'
@echo ' targz-pkg - Build the kernel as a gzip compressed tarball'
@echo ' tarbz2-pkg - Build the kernel as a bzip2 compressed tarball'
+ @echo ' tarxz-pkg - Build the kernel as a xz compressed tarball'
@echo ' perf-tar-src-pkg - Build $(perf-tar).tar source tarball'
@echo ' perf-targz-src-pkg - Build $(perf-tar).tar.gz source tarball'
@echo ' perf-tarbz2-src-pkg - Build $(perf-tar).tar.bz2 source tarball'
+ @echo ' perf-tarxz-src-pkg - Build $(perf-tar).tar.xz source tarball'
--- a/scripts/package/buildtar 2011-01-28 23:05:03.000000000 +0100
+++ b/scripts/package/buildtar 2011-01-28 23:08:20.000000000 +0100
@@ -35,6 +35,10 @@
compress="bzip2 -c9"
file_ext=".bz2"
;;
+ tarxz-pkg)
+ compress="xz -c9"
+ file_ext=".xz"
+ ;;
*)
echo "Unknown tarball target \"${1}\" requested, please add it to ${0}." >&2
exit 1
next reply other threads:[~2011-01-28 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 22:21 Zdenek Kaspar [this message]
2011-01-30 11:18 ` Add make tarxz-pkg build option Zdenek Kaspar
2011-02-24 15:57 ` Michal Marek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D43417A.1020603@gmail.com \
--to=zkaspar82@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.