Am Samstag, den 03.11.2007, 00:31 +0100 schrieb Daniel Leidert: > Am Freitag, den 02.11.2007, 20:27 +0100 schrieb David Paleino: [..] > > I might agree that we save space by avoiding duplication of source code, yes, > > but I find it far less intuitive to, for example, create a patch for the source > > code: actually, in fact, I have to create the patch in some other dir where I > > have the source code extracted, svn commit it, svn up from the "real" > > directory, and svn-buildpackage from there. Probably I'm missing something, and > > I would be thankful for anyone who would save me from this hell. > > I use the first example (no source files except the debian packaging > files). If you use dpatch, you can do the following: [snip] I attached a sample dpatch.conf. Adjust the paths and then try a dpatch-edit-patch -b mynewpatch I tested it successfully here. Unfortunately I do not use quilt. If it supports something like the -b option of dpatch-edit-patch too I'm sure, you can implement the same solution for quilt. If it does not support this type of layout, maybe you should send a bug report. Regards, Daniel
Attachment:
.dpatch.conf
Description: application/pak