On 9/22/07, Frank Lichtenheld <[EMAIL PROTECTED]> wrote: > On Thu, Aug 02, 2007 at 08:33:05PM +0200, Raphael Hertzog wrote: > A good opportunity to change the default behaviour of dpkg-source would > be the addition of wig&pen build support, BTW ;)
The problem with generating W&P format is that you need to provide more information about how the package is constructed than is given to an invocation of "dpkg-source -b" which has only the .orig dir or .orig.tar.gz and the current dir. Given those basic input, the most sensible output is v1.0 format. So, while dpkg-source needs to be able to parse W&P format, the task of creating it should fall to tools better suited to the job: think git-buildpackage and other such tools which should have knowledge of a discrete set of patches/changesets. Note that parse support in dpkg-source still allows for a package to be unpacked/edited/rebuilt (albeit in a "lossy" way) by a local admin, the security team or whoever using only dpkg-dev tools. dpkg-source -x pack.dsc # unpack v2.0 [edit] dpkg-buildpackage ... # create v1.0 --bod -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
