On Fri, Nov 20, 2009 at 11:28:56AM +0100, Marco Nenciarini wrote: > 2) Talking of an hypothetic VCS-buildpackage using pristine-tar or > similar tools, how it can known which component tarball need it to > extract to create the right build environment? May be we should > define a standard place under the debian/source directory for such > information.
I think we should too.
A recurring devscript request (which will become even more recurring now
with 3.0 and multi-origin) is to have support for downloading multiple
tarballs in uscan. See #531321 for more details.
In essence, the problem can be summarized as follows. Uscan is aware
only of one source tarball, and of only one current package version. The
former part is easy to fix (it amount to supporting multi-tarball
debian/watch file); the latter part is harder, because uscan has only
changelog to know latest upstream version imported available in Debian.
Having a place where to write which 3.0 tarballs compose the final "orig
upstream source" *and* the latest version imported into Debian will
solve both yours and the uscan problem.
Note that the uscan problem is not just a matter of making easy to
download several tarballs at once, but is rather part of the workflow we
now need to manage multi-tarballs packages (e.g. I want to be notified
when a single tarball of a whole got a new upstream release; currently
this is not doable with available tools).
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime
signature.asc
Description: Digital signature
