On Sat, 24 May 2008, Laurence J. Lane wrote: > You don't understand because that task is not the focus. The package > build is messy. Any number of error prone contortions can be used > to clean the mess. git reverts the whole thing to origin quite > painlessly and quiltimport is a bonus that dropped a dependency.
Ok. I saw packages (like lvm2, devmapper) where they copy the source tree to a temporary directory... that would do the trick as well. Anyway a comment in your rules file explaining why you decided to use git in your build process is always welcome so that people (like me) can understand your choice. Coming back to the problem, when you use quilt directly, the .pc directorty is created and quilt won't reapply the patches twice. In your case if you don't want to use quilt, you have the possibility to check for debian/patches/.dpkg-source-applied to verify if the patches have been applied. > dpkg-source(1) shows three different Format 3.0 formats (native, > custom and quilt) and two additional experimental (git and bzr). As > far as I can see, none of them are currently supported by Debian's > archive tools. But the fact that there are so many, alludes to some > sort of choice between them. Is Format 3.0 quilt really going to be > the only one supported? It's the one (together with the "native" one) that I (as dpkg maintainer) asked ftp-masters to officially support in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457345 Unless the ftp-masters have good reasons to make another decision, I hope that this will be the case. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
