From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
"Enrico Weigelt, metux IT consult" <info@metux.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Robo Bot <apw@canonical.com>, Joe Perches <joe@perches.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
linux-riscv@lists.infradead.org,
clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [PATCH 4/4] debian: add generic rule file
Date: Wed, 17 Jul 2019 16:16:39 +0200 [thread overview]
Message-ID: <77f82ca2-f89b-e8e2-507a-c37bce1343a5@metux.net> (raw)
In-Reply-To: <20190716123431.GB2999@mit.edu>
On 16.07.19 14:34, Theodore Y. Ts'o wrote:
Hi,
> In practice, that's not going to be a problem for most distributions.
> The traditional way Debian-derived systems have done builds is
> completely outside of git. So there will be a linux_5.2.orig.tar.gz
> and a linux_5.2-1.debian.tar.xz. dpkg_source -x will first unpackage
> the orig.tar.gz, and then the debian.tar.xz, and if the second
> overwrites the first, it's no big deal.
ACK. IIRC they already filter out debian/ directories when generating
upstream tarballs - other upstreams already provide their debian/
stuff, too.
> First, once it's checked in, I expect changes to the default
> debian/rules file will be relatively rare.
ACK. I currently don't see much reasons for future changes. If anybody
sees something missing, just let me know, and I'll take it up for the
next review round.
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2019-07-17 14:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-09 9:32 [PATCH 1/4] Makefile: rules for printing kernel architecture and localversion Enrico Weigelt, metux IT consult
2019-07-09 9:32 ` [PATCH 2/4] scripts: mkdebian: allow renaming generated debian/rules via env Enrico Weigelt, metux IT consult
2019-07-09 9:32 ` [PATCH 3/4] scripts: checkpatch.pl: don't complain that debian/rules is executable Enrico Weigelt, metux IT consult
2019-07-09 10:16 ` Joe Perches
2019-07-09 9:32 ` [PATCH 4/4] debian: add generic rule file Enrico Weigelt, metux IT consult
2019-07-15 12:28 ` Masahiro Yamada
2019-07-15 18:56 ` Enrico Weigelt, metux IT consult
2019-07-15 19:12 ` Theodore Y. Ts'o
2019-07-16 8:58 ` Masahiro Yamada
2019-07-16 12:34 ` Theodore Y. Ts'o
2019-07-17 14:16 ` Enrico Weigelt, metux IT consult [this message]
2019-07-17 15:23 ` Theodore Y. Ts'o
2019-07-17 11:08 ` Enrico Weigelt, metux IT consult
2019-07-09 14:54 ` [PATCH 1/4] Makefile: rules for printing kernel architecture and localversion Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2019-02-07 16:40 RFC: refactoring the deb build Enrico Weigelt, metux IT consult
2019-02-07 16:40 ` [PATCH 4/4] debian: add generic rule file Enrico Weigelt, metux IT consult
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=77f82ca2-f89b-e8e2-507a-c37bce1343a5@metux.net \
--to=lkml@metux.net \
--cc=apw@canonical.com \
--cc=clang-built-linux@googlegroups.com \
--cc=info@metux.net \
--cc=joe@perches.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=michal.lkml@markovi.net \
--cc=tytso@mit.edu \
--cc=yamada.masahiro@socionext.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®