From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from outgoing-auth-1.mit.edu ([18.9.28.11]:55714 "EHLO outgoing.mit.edu" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725948AbfGQPYC (ORCPT ); Wed, 17 Jul 2019 11:24:02 -0400 Date: Wed, 17 Jul 2019 11:23:26 -0400 From: "Theodore Y. Ts'o" Subject: Re: [PATCH 4/4] debian: add generic rule file Message-ID: <20190717152326.GC31412@mit.edu> References: <1562664759-16009-1-git-send-email-info@metux.net> <1562664759-16009-4-git-send-email-info@metux.net> <5af9db32-2cf5-10ba-261c-e08852d0814f@metux.net> <20190715191245.GD3068@mit.edu> <20190716123431.GB2999@mit.edu> <77f82ca2-f89b-e8e2-507a-c37bce1343a5@metux.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <77f82ca2-f89b-e8e2-507a-c37bce1343a5@metux.net> Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: "Enrico Weigelt, metux IT consult" Cc: Masahiro Yamada , "Enrico Weigelt, metux IT consult" , Linux Kernel Mailing List , Michal Marek , Robo Bot , Joe Perches , Linux Kbuild mailing list , linux-riscv@lists.infradead.org, clang-built-linux On Wed, Jul 17, 2019 at 04:16:39PM +0200, Enrico Weigelt, metux IT consult wrote: > > > 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. Well, no, actually they don't. That's because as much as possible they want the upstream tarball to be bit-for-bit identical to the one published on the official upstream distribution site. That allows them to include the detached PGP signature from the upstream maintainer, if one is provided. If there are files in the upstream debian/ directory that they don't need, they can delete in the distro's debian/rules file. Ideally, so we shouldn't include files in the Linux kernel's debian/ directory willy-nilly. But the debian/rules file will *always* be present, and so it will be overwritten by the _.debian.tar.xz file, and so it's no big deal. - Ted From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 536ACC7618F for ; Wed, 17 Jul 2019 15:23:48 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 1EEDC2145D for ; Wed, 17 Jul 2019 15:23:48 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="WvL70RsU" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1EEDC2145D Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=mit.edu Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=U9V/l1GUV36JxT0wOiqRbkSM3rqFpEufQAsCw4YxaOI=; b=WvL70RsUkc14+3 Sdz+TgW3v/0erDh9rNgRqwAyh1vux92oo9WbjnXRN6/jtOnInnXkonsNlaPzua3AETU3NlRMHmAfN TE4jlrHJq/gnrx4La/wEpGVhHzNwGOXOUUDakupPsO1BSoc8m0MGUqOafbsGQFh9FSkwtZvG5EQhy G/5N++HNbt/lHg3JKgn56sd98+kEDHXtt8hhncddzZulBDRQs9NGejTglOdCwV+RGmSHD+uDbw5Gp AziVv79CEtc6bFwr6rDF4hyKTfP/LDSEcb5QV3MxzNO/m5ISorKR5X8lyIp+AD2DpW08SvmghkjOO y/2b/vTgoxPnUH17pXiQ==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hnlmQ-0000FS-FX; Wed, 17 Jul 2019 15:23:42 +0000 Received: from outgoing-auth-1.mit.edu ([18.9.28.11] helo=outgoing.mit.edu) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1hnlmM-0000Eh-6C for linux-riscv@lists.infradead.org; Wed, 17 Jul 2019 15:23:40 +0000 Received: from callcc.thunk.org (guestnat-104-133-0-99.corp.google.com [104.133.0.99] (may be forged)) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x6HFNQK1019058 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 17 Jul 2019 11:23:27 -0400 Received: by callcc.thunk.org (Postfix, from userid 15806) id 5AE86420054; Wed, 17 Jul 2019 11:23:26 -0400 (EDT) Date: Wed, 17 Jul 2019 11:23:26 -0400 From: "Theodore Y. Ts'o" To: "Enrico Weigelt, metux IT consult" Subject: Re: [PATCH 4/4] debian: add generic rule file Message-ID: <20190717152326.GC31412@mit.edu> Mail-Followup-To: "Theodore Y. Ts'o" , "Enrico Weigelt, metux IT consult" , Masahiro Yamada , "Enrico Weigelt, metux IT consult" , Linux Kernel Mailing List , Michal Marek , Robo Bot , Joe Perches , Linux Kbuild mailing list , linux-riscv@lists.infradead.org, clang-built-linux References: <1562664759-16009-1-git-send-email-info@metux.net> <1562664759-16009-4-git-send-email-info@metux.net> <5af9db32-2cf5-10ba-261c-e08852d0814f@metux.net> <20190715191245.GD3068@mit.edu> <20190716123431.GB2999@mit.edu> <77f82ca2-f89b-e8e2-507a-c37bce1343a5@metux.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <77f82ca2-f89b-e8e2-507a-c37bce1343a5@metux.net> User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190717_082338_639746_1B87EE81 X-CRM114-Status: GOOD ( 10.76 ) X-BeenThere: linux-riscv@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Michal Marek , Linux Kbuild mailing list , Linux Kernel Mailing List , Masahiro Yamada , clang-built-linux , Robo Bot , Joe Perches , linux-riscv@lists.infradead.org, "Enrico Weigelt, metux IT consult" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-riscv" Errors-To: linux-riscv-bounces+infradead-linux-riscv=archiver.kernel.org@lists.infradead.org On Wed, Jul 17, 2019 at 04:16:39PM +0200, Enrico Weigelt, metux IT consult wrote: > > > 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. Well, no, actually they don't. That's because as much as possible they want the upstream tarball to be bit-for-bit identical to the one published on the official upstream distribution site. That allows them to include the detached PGP signature from the upstream maintainer, if one is provided. If there are files in the upstream debian/ directory that they don't need, they can delete in the distro's debian/rules file. Ideally, so we shouldn't include files in the Linux kernel's debian/ directory willy-nilly. But the debian/rules file will *always* be present, and so it will be overwritten by the _.debian.tar.xz file, and so it's no big deal. - Ted _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv