On July 21, 2015 04:46:40 PM Paul Novotny wrote: > On Mon, 2015-07-20 at 11:34 -0500, Steve M. Robbins wrote: > > 1. Upstream now separates the test data from the source tarball. I > > would like > > to keep the tests so I planned to use the "multiple orig tarball" > > feature. I > > believe I've done it before with ITK but last week "svn buildpackage" > > failed > > me. Need to figure this out. > > I can help with this. Do you have a branch that you used to try this > out? I do not know anything about "multiple orig tarball", but saw this > blog post: > > https://raphaelhertzog.com/2010/09/07/how-to-use-multiple-upstream > -tarballs-in-debian-source-packages/ Yep, that's the one. The trouble I had appears to be related to the leading dot in the directory name! I had tried naming the data tarball as insighttoolkit4_4.8.0.orig-.ExternalData.tar.xz (notice "." after "orig-") because I wanted it unpacked into ".ExternalData". But "debuild -S" just ignored it. When I removed the dot, it works! So after naming it insighttoolkit4_4.8.0.orig-ExternalData.tar.xz, I have the multi-tarball source working. However, that puts the data into "<topdir>/ExternalData/.ExternalData",which is not where the build looks by default. So I also set the ExternalData_OBJECT_STORES you pointed out (thanks!). Now it builds. > And looked at libcgi-application-perl, which has multiple tarballs. > They seam to have created an debian/update.sh, that looks at multiple > watch files (in debian/components). Is this something along the lines > of what you were thinking? I hadn't considered that, but it sounds like a good idea. -Steve
Attachment:
signature.asc
Description: This is a digitally signed message part.