Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod From: Julian Gilbey Newsgroups: linux.debian.devel.mentors,linux.debian.maint.python Subject: Re: How to create multi-source tarball with different submodules for scipy Date: Mon, 16 Jan 2023 18:10:01 +0100 Message-ID: References: X-Mailbox-Line: From debian-mentors-request@lists.debian.org Mon Jan 16 17:07:54 2023 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.2 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5] autolearn=unavailable autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -4.6 X-Greylist: delayed 2374 seconds by postgrey-1.36 at bendel; Mon, 16 Jan 2023 17:07:36 UTC MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailing-List: archive/latest/109304 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/Y8V7D59Ikt7WFXZo@d-and-j.net Approved: robomod@news.nic.it Lines: 23 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Debian Mentors List , Debian Python X-Original-Date: Mon, 16 Jan 2023 16:27:59 +0000 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.devel.mentors:45889 linux.debian.maint.python:14828 On Mon, Jan 16, 2023 at 05:05:39PM +0100, Andreas Tille wrote: > Hi, > > I tried to create a multi-source tarball for scipy in its experimental > branch[1]. Upstream includes a set of git submodules in its build > process. I intended to merge all these submodules in a single > scipy_1.10.0.orig-submodules.tar.gz. This tarball is created with a > script[2] which makes sure that the exact directory structure as it is > used by upstream is conserved. This directory layout is needed in the > build process. Unfortunately `dpkg-source -x` extracts the content of > the submodules tarball into a subdirectory submodules/. > > Is there any trick to unpack this tarball right into the root? > Otherwise I need to do some symlinks workaround in d/rules to provide > all files where these are needed. Not that I know of; this is the design of the multi-source tarball setup: each component tarball is extracted into a directory with the name of the component. Best wishes, Julian