Report forwarded to debian-bugs-dist@lists.debian.org, Charles Briscoe-Smith <cpbs@debian.org>:
Bug#52711; Package yada.   debian-bugs-dist@lists.debian.orgCharles Briscoe-Smith  Subject: Bug#52711: yada util to generate patches Reply-To: Samuel Tardieu , 52711@bugs.debian.org Resent-From: Samuel Tardieu Orignal-Sender: sam@antinea.enst.fr Resent-To: debian-bugs-dist@lists.debian.org Resent-CC: Charles Briscoe-Smith Resent-Date: Tue, 14 Dec 1999 15:18:02 GMT Resent-Message-ID: Resent-Sender: owner@bugs.debian.org X-Debian-PR-Message: report 52711 X-Debian-PR-Package: yada X-Debian-PR-Keywords: X-Loop: owner@bugs.debian.org Received: via spool by bugs@bugs.debian.org id=B.94518431817704 (code B ref -1); Tue, 14 Dec 1999 15:18:02 GMT From: Samuel Tardieu To: Debian Bug Tracking System X-Reportbug-Version: 0.46 X-Mailer: reportbug 0.46 Date: Tue, 14 Dec 1999 15:45:05 +0100 Message-Id: <19991214144505.BD8C010F12@antinea.enst.fr> Sender: sam@antinea.enst.fr Package: yada Version: 0.9 Severity: wishlist I use the Patches: line for all my packages to keep my changes in distinct and clearly identifiable patch files. However, generating a patch file is a pain: - copy the file you want to modify in file.orig - edit file - diff -u file.orig file > debian/newpatch.dpatch - edit debian/newpatch.dpatch to add #PATCHOPTIONS: -p0 - move file.orig to file back Now, let's imagine that yada makes a build-directory (under debian/ maybe) and builds everything in this build-directory after making a copy of the source. This would let the source untouched. If I want to modify "file", I could go in the build-directory, where I could find the package source already patched by the other patches. I can then modify "file" there, and launch "yada makepatch debian/newpatch.dpatch". yada would compare the current sources against the pristine sources (found just above) + the other patches already applied, and generate a new patch file debian/newpatch.dpatch containing the difference made to "file", with the right PATCHOPTIONS added. Well, that's not easy to explain, but did you get the idea? Moreover, the idea of having a debian/build-directory is that making a "debuild clean" is easier: just remove debian/build-directory, debian/tmp-*, debian/*-stamp, etc. One more reason to do this is that I have packages that modify binary files that belong to the distribution (and that are needed to build the package, such as byte codes for building Erlang). In my scripts, I have to preserve the original files at the beginning of the build and restore them at clean time. This is painful. -- System Information Debian Release: potato Architecture: i386 Kernel: Linux antinea 2.2.13 #1 Mon Nov 8 12:40:02 CET 1999 i686 Versions of packages yada depends on: ii dpkg-dev 1.6.3 Package building tools for Debian ii perl-5.004 [perl5] 5.004.05-3 Larry Wall's Practical Extracting ii perl-5.005 [perl5] 5.005.03-4 Larry Wall's Practical Extracting   Acknowledgement sent to Samuel Tardieu <sam@debian.org>:
New Bug report received and forwarded. Copy sent to Charles Briscoe-Smith <cpbs@debian.org>.   -t  From: owner@bugs.debian.org (Debian Bug Tracking System) To: Samuel Tardieu Subject: Bug#52711: Acknowledgement (yada util to generate patches) Message-ID: In-Reply-To: <19991214144505.BD8C010F12@antinea.enst.fr> References: <19991214144505.BD8C010F12@antinea.enst.fr> X-Debian-PR-Message: ack 52711 Thank you for the problem report you have sent regarding Debian. This is an automatically generated reply, to let you know your message has been received. It is being forwarded to the developers mailing list for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Charles Briscoe-Smith If you wish to submit further information on your problem, please send it to 52711@bugs.debian.org (and *not* to bugs@bugs.debian.org). Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Darren Benham (administrator, Debian Bugs database)   Received: (at submit) by bugs.debian.org; 14 Dec 1999 15:11:58 +0000 Received: (qmail 17702 invoked from network); 14 Dec 1999 15:11:58 -0000 Received: from marvin.enst.fr (HELO ada.eu.org) (postfix@137.194.161.2) by master.debian.org with SMTP; 14 Dec 1999 15:11:58 -0000 Received: from antinea.enst.fr (antinea.enst.fr [137.194.160.145]) by ada.eu.org (Postfix) with ESMTP id 8F4E519072; Tue, 14 Dec 1999 16:11:54 +0100 (CET) Received: by antinea.enst.fr (Postfix, from userid 1000) id BD8C010F12; Tue, 14 Dec 1999 15:45:05 +0100 (CET) From: Samuel Tardieu To: Debian Bug Tracking System Subject: yada util to generate patches X-Reportbug-Version: 0.46 X-Mailer: reportbug 0.46 Date: Tue, 14 Dec 1999 15:45:05 +0100 Message-Id: <19991214144505.BD8C010F12@antinea.enst.fr> Sender: sam@antinea.enst.fr Package: yada Version: 0.9 Severity: wishlist I use the Patches: line for all my packages to keep my changes in distinct and clearly identifiable patch files. However, generating a patch file is a pain: - copy the file you want to modify in file.orig - edit file - diff -u file.orig file > debian/newpatch.dpatch - edit debian/newpatch.dpatch to add #PATCHOPTIONS: -p0 - move file.orig to file back Now, let's imagine that yada makes a build-directory (under debian/ maybe) and builds everything in this build-directory after making a copy of the source. This would let the source untouched. If I want to modify "file", I could go in the build-directory, where I could find the package source already patched by the other patches. I can then modify "file" there, and launch "yada makepatch debian/newpatch.dpatch". yada would compare the current sources against the pristine sources (found just above) + the other patches already applied, and generate a new patch file debian/newpatch.dpatch containing the difference made to "file", with the right PATCHOPTIONS added. Well, that's not easy to explain, but did you get the idea? Moreover, the idea of having a debian/build-directory is that making a "debuild clean" is easier: just remove debian/build-directory, debian/tmp-*, debian/*-stamp, etc. One more reason to do this is that I have packages that modify binary files that belong to the distribution (and that are needed to build the package, such as byte codes for building Erlang). In my scripts, I have to preserve the original files at the beginning of the build and restore them at clean time. This is painful. -- System Information Debian Release: potato Architecture: i386 Kernel: Linux antinea 2.2.13 #1 Mon Nov 8 12:40:02 CET 1999 i686 Versions of packages yada depends on: ii dpkg-dev 1.6.3 Package building tools for Debian ii perl-5.004 [perl5] 5.004.05-3 Larry Wall's Practical Extracting ii perl-5.005 [perl5] 5.005.03-4 Larry Wall's Practical Extracting