Barry Warsaw <ba...@debian.org> writes: > On Dec 04, 2013, at 01:36 PM, Stuart Prescott wrote: > > >Having uscan call "debian/rules get-orig-source" is quite difficult to do in > >a policy-compliant way (as already noted by Jakub) as the location for the > >munged tarball is different. Having uscan call a debian/repack from d/watch > >seems a little more sane only because there's no policy saying what d/repack > >must do; having uscan do the repacking itself with something like Files- > >Excluded from d/copyright is even nicer and devscripts in git can do this. > > If you have a good example of a d/repack recipe, please do add it to the > LibraryStyleGuide wiki page.
We already have <URL:https://wiki.debian.org/onlyjob/get-orig-source>, in particular <URL:https://wiki.debian.org/onlyjob/get-orig-source#Repackaging_orig.tar>. Are you expecting ‘debian/repack’ to be significantly different when repacking Python-language packages, as opposed to the general case of repacking an upstream source tarball? What differences would be great enough to warrant a Python-library-specific recipe? -- \ “It is the mark of an educated mind to be able to entertain a | `\ thought without accepting it.” —Aristotle | _o__) | Ben Finney -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7wiov3oiyp....@benfinney.id.au