On Tue, Apr 12, 2005 at 10:29:10PM +0900, Junichi Uekawa wrote: > > > unpack: some packages unpack the upstream tarball, some do patching > > > patch: some patch the source tree, some generate patch out of it. > > 2. A policy on what target to have for optional unpacking and patching, > > and apply a recommendation that is enforced on etch/etch+1 > > > > That should probably not be unpack/patch since they break existing > > makefiles, and as #250202 suggests, unpacked and patched seem to be > > good candidates. > > > > I'm going to check the output of > > > > make -f debian/rules -n -p | grep '^[^ ]\+:' | grep -v '^#' > > > > to make sure what targets don't exist. > > > I've found out that the status is : > > patched -- unused > unpacked -- used > unpack -- used > patch --used
I am not sure it is relevant, but there is two way to use dpatch: either you make clean depend on patch or on unpatch. If clean depend on patch, then every patches are already applied when running dpkg-source -x so you don't need to run debian/rules patch. Some packages actually do that. Maybe you want to check that. Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
