Author astraw
Recipients alberanid, anadelonbrin, astraw, barry, dairiki, ebfe, eric.araujo, jafo, kbk, leonidasxiv, loewis, rockstar, tarek
Date 2010-04-29.18:21:45
SpamBayes Score 5.57578e-07
Marked as misclassified No
Message-id <1272565306.8.0.156427459786.issue1054967@psf.upfronthosting.co.za>
In-reply-to
Content
Barry, I'm sorry I still don't understand what you think is the essential distinction. A debian source package (.dsc, .orig.tar.gz, and .diff.gz files) is simply made from a (patched) source directory, including the debian/ directory, and an upstream tarball. To build this sdist_dsc must of course make the debian/ directory. Thus, it "takes a non-Debianized source tree and turn it into a native [Debian source] package, essentially by pre-filling a debian/ directory like dh_make does, but including additional metadata available in the setup.py". Then, once it done this, it calls "dpkg-buildpackage -S" to turn this filesystem structure into the actual source package. If your final goal is simply the filesystem structure rather than the Debian source package (.dsc, .orig.tar.gz and .diff.gz), then it seems like it would be easier to refactor stdeb to stop before calling dpkg-buildpackage rather than writing a whole new alternate way of generating the debian/ directory based on the contents of setup.py.

So I'm afraid I still don't understand what you want setupdebian to do that stdeb does not.
History
Date User Action Args
2010-04-29 18:21:47astrawsetrecipients: + astraw, loewis, barry, kbk, jafo, anadelonbrin, dairiki, alberanid, leonidasxiv, tarek, eric.araujo, rockstar, ebfe
2010-04-29 18:21:46astrawsetmessageid: <1272565306.8.0.156427459786.issue1054967@psf.upfronthosting.co.za>
2010-04-29 18:21:45astrawlinkissue1054967 messages
2010-04-29 18:21:45astrawcreate