On Tuesday, November 19, 2024 3:39:06 PM MST Hilmar Preuße wrote:

Hello,

I hope this is an easy question: the new version of asymptote downloads additional tar balls (two) during configure, which are unpackaged and
used during build. Page [1] describes how to add additional tar balls.
It says, that the name (extension) of the additional tar ball determines
the subdir the tar ball is extracted to. I need the additional source
code in acextlibs/vectorgraphics/LspCpp & acextlibs/syoyo/tinyexr .

That is correct, but I don’t think it handles subdirectories. So, for example, if the second tarball has a component name of `acextlibs` it will be extrated to the `acextlibs` directory (I have no idea how the system behaves if the `acextlibs` directory already exists). If its contents are inside of `vectorgraphics/LspCP`, then you should be fine. But if the contents of the tarball are in the root directory of the tarball, I don’t think MUT (Multiple
Upstream Tarballs) has any provisions for unpacking them to `acextlibs/ vectorgraphics/LspCpp`.

To see a live example, check out fonts-adobe-sourcesans3.

https://salsa.debian.org/fonts-team/fonts-adobe-sourcesans3/-/blob/master/ debian/watch?ref_type=heads

https://salsa.debian.org/fonts-team/fonts-adobe-sourcesans3/-/blob/master/ debian/README.Source?ref_type=heads

--
Soren Stoutner
soren@debian.org
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmc+Q4UACgkQwufLJ66w tgOJJQ//W6ACSE3bXzc3MQQwylWTBCXQGiZ1Whn/ObApWRhS7Ndr5GI8S2MIUsKs wMpbdsPfHafInx5KEp/QCAvqAP33O3c8rhN5jWE60DSAyTkTZghZwbLnon6Nx45h K8rwZXwiYxz1TqoODEJ4hr3FQj64KzXByhoVGqnOLj/5di0ARDCagEkZQ/HlUMFm 6rSRWG76DdmXl0vuY4s/h53p/rYvYAEH/sYT9tXqOVL9PWnp97sE9tqjbh8+0ash efwapyf4RmQXUaYxYhWVnpRckB4XYZCeH2r/zZkMwcB0fH4AUa5ltfqKUvIItgE1 VIwicekDbr0RqHK7iSFD/5IRcsuGTS0dIHSJ7u0BNaq6Ruc1fSSd8iR1KH6brJP+ lytxDUpkISoIVNvqijCsXjcl46aYRij/pZ3vMMHCLVlO91koO2Q0teUpBNgRT2Xa FoUuitTyH5tTns7qXxxCQjAlhVF6QSDtk3kKF1BZOxEWIqGGJUWb+mdM71W9Vcdk w5khP1wwLYi0o3HTPOPzhOuJT4MbH1GF1x/REPCjyE2K8AmscxlJp3k3qo1pPz7u xFMs7sQcqwm9vvCQAEmI6q//VUJ4H5/xgLs2oKeLb+yrschrO/6eIn/UnNQI4W3P PzzKqD6AKfY1fsGBIridcFVRckC1Y8e6x74bDXXvjtQdNZKRABo=
=nlLu
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Copy: hille42@web.de (=?ISO-8859-1?Q?Preu=DFe=2C?= Hilmar)

On Tuesday, November 26, 2024 3:42:39 PM MST Preuße, Hilmar wrote:

Am 19.11.2024 um 23:39 schrieb Hilmar Preuße:

Hi,

How do I have to name the additional tar balls? Putting the needed directory into the tar balls does not seem to do the trick. Currently my only idea is to merge the two tar balls into one and name it asy....orig-acextlibs.tar.xz .

Hopefully(?) last question. I use gbp and master/upstream/pristine-tar branch The source package now consists of three different orig.tar.xz
files. Where should I put the files into the repo? putting the two new
files into the existing pristine-tar branch probably doesn't make sense. Should I simply two new branches and put them there? The file d/README.source exists anyway.

The following example with fonts-adobe-sourcesans3 might be helpful, even if it is a little different than your situation.

I created the following MUT repository using `gbp import-dsc`:

https://salsa.debian.org/fonts-team/fonts-adobe-sourcesans3

It put both tarballs in pristine-tar.

Building a package with MUT from pristine-tar requires some extra info with the --git-component argument (which I believe can be specified multiple times).

https://salsa.debian.org/fonts-team/fonts-adobe-sourcesans3/-/blob/master/ debian/README.Source?ref_type=heads#L49-75

I should note that I haven’t actually tried the `gbp import-orig` code path for importing a new release, as this font package hasn’t had a new release since I created it. It is based simply on reading the documentation (which I might have misunderstood).

--
Soren Stoutner
soren@debian.org
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmdGkqcACgkQwufLJ66w tgP4qg/+MlQGSr6JNyZ+3Fy6qx7EgP9QWyQmjmV3w0j6sTUlqrTMsHY4Xpot1fGt LifWmnS/W7p8aAgV9ZFq51T5AHwMrYV2hxJuNjiuXZC36+jdAQ2yZkIRrWgToZzO YVDpyc282Mv1lNfnzrzht1yp9hOGsk4mAbGBYZXNQzS7zo9LTDZl/bPzDdGjPpHg /LNpm5/R7H7tj9gjIhLNCa8OmtlYm64iNU7ZWzKpiEpmUnngQzGDmvy5dLeh5tlf 0ARpQ9n4iwdG7xpSH5zrubagJT1Y34ae6lxcyCyrd1+fH5Hx441UX1/2Cxh1zPrP nco7TIUaqFpfNld57kD6LRMWprNA9mqGK8Fsk+b/1SF71ZBL+msDowOuoD1WLSJE 3JaDLScPJnX6R+y3T1D2qNNtag8MaBRpUIZ21ykS6oOsPyD8H+TrzZ3SO0HAZZy3 FTloHv5WcU3iNYr6eh3Qgb4/u+TIrwdZmgX7ubnsqe6SFAxpjPR4ZwxmcPsjWysk h6x4fMguqsV/tC8baOTfbBciuSCqaZZJh94/O1x++fmOndwytmrUExnmthmEo/hm Z5P8XuTW1YV3zmA3TWAyToIh1UX8Q2W9zcf/gsMV2LEcnDUlA1J814nPYztD1Cg6 DHZODTiwse4Ua1/y0gm6hMG3knNViZ9J7+vMsxv/rKa1PcYjrfY=
=2p/6
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)