Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.devel.mentors > #45888 > unrolled thread

How to create multi-source tarball with different submodules for scipy

Started byAndreas Tille <andreas@an3as.eu>
First post2023-01-16 17:10 +0100
Last post2023-01-17 22:50 +0100
Articles 4 — 4 participants

Back to article view | Back to linux.debian.devel.mentors


Contents

  How to create multi-source tarball with different submodules for  scipy Andreas Tille <andreas@an3as.eu> - 2023-01-16 17:10 +0100
    Re: How to create multi-source tarball with different submodules for  scipy Julian Gilbey <julian@d-and-j.net> - 2023-01-16 18:10 +0100
      Re: How to create multi-source tarball with different submodules for scipy Soren Stoutner <soren@stoutner.com> - 2023-01-16 19:20 +0100
    Re: How to create multi-source tarball with different submodules for scipy Nick Morrott <knowledgejunkie@gmail.com> - 2023-01-17 22:50 +0100

#45888 — How to create multi-source tarball with different submodules for scipy

FromAndreas Tille <andreas@an3as.eu>
Date2023-01-16 17:10 +0100
SubjectHow to create multi-source tarball with different submodules for scipy
Message-ID<FOAdz-QJZ-1@gated-at.bofh.it>
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.

Kind regards
   Andreas.

[1] https://salsa.debian.org/python-team/packages/scipy/-/tree/experimental
[2] https://salsa.debian.org/python-team/packages/scipy/-/blob/experimental/debian/get-submodules

-- 
http://fam-tille.de

[toc] | [next] | [standalone]


#45889

FromJulian Gilbey <julian@d-and-j.net>
Date2023-01-16 18:10 +0100
Message-ID<FOAwV-QQP-3@gated-at.bofh.it>
In reply to#45888
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

[toc] | [prev] | [next] | [standalone]


#45890 — Re: How to create multi-source tarball with different submodules for scipy

FromSoren Stoutner <soren@stoutner.com>
Date2023-01-16 19:20 +0100
SubjectRe: How to create multi-source tarball with different submodules for scipy
Message-ID<FOCfn-RZh-9@gated-at.bofh.it>
In reply to#45889

[Multipart message — attachments visible in raw view] — view raw

I haven’t looked closely at it myself, but qtwebengine-opensource-src accomplishes 
something along these lines using `get-orig-source` in their rules file.

https://salsa.debian.org/qt-kde-team/qt/qtwebengine/-/blob/master/debian/rules[1]

Note that, in their case, you must have the python3-debian package installed, because the 
script depends on Python for some of the processing.

On Monday, January 16, 2023 9:27:59 AM MST Julian Gilbey wrote:
> 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


-- 
Soren Stoutner
soren@stoutner.com

--------
[1] https://salsa.debian.org/qt-kde-team/qt/qtwebengine/-/blob/master/debian/rules

[toc] | [prev] | [next] | [standalone]


#45900 — Re: How to create multi-source tarball with different submodules for scipy

FromNick Morrott <knowledgejunkie@gmail.com>
Date2023-01-17 22:50 +0100
SubjectRe: How to create multi-source tarball with different submodules for scipy
Message-ID<FP209-18dj-5@gated-at.bofh.it>
In reply to#45888
On Mon, 16 Jan 2023 at 16:06, Andreas Tille <andreas@an3as.eu> 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.

When I packaged firmware-microbit-microbit I wasn't aware of any
tricks, so I resorted to overriding dh_auto_build to move the
extracted components into their expected paths before building:

https://salsa.debian.org/python-team/packages/firmware-microbit-micropython/-/blob/debian/master/debian/rules

Not sure if this useful, but I thought I'd pass it along in case it helps.

Cheers,
Nick

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.devel.mentors


csiph-web