Re: (un)patching patched files

2012-10-10 Thread Jasmine Hassan
override_dh_autoreconf: post_patch dh_autoreconf override_dh_auto_clean: if [ -d src/orig-dir -a -d debian/tmp ]; then debian/rules post_patch; fi dh_auto_clean Hope that helps anyone :) On Wed, Oct 10, 2012 at 4:37 AM, Jasmine Hassan wrote: > Hi, > > Has this been reported as a bug yet? >

Re: Re: Renaming files, patching, renaming files, unpatching, and 3.0(quilt)

2012-10-10 Thread Jasmine Hassan
y* in this. Best, Jasmine On Wed, Oct 10, 2012 at 9:14 PM, Jasmine Hassan wrote: > Thibaut Paumard writes: > >> Raphaël is right: >> - you should try to collaborate with other distributions on a >> *single* fork. >> - your fork should not be called "compi

Re: Re: Renaming files, patching, renaming files, unpatching, and 3.0(quilt)

2012-10-10 Thread Jasmine Hassan
Thibaut Paumard writes: > Raphaël is right: > - you should try to collaborate with other distributions on a > *single* fork. > - your fork should not be called "compiz", please pick a unique > name, such as compiz-mate or matepiz or whatever > There are no distributions. Only a fork

Re: Re: Renaming files, patching, renaming files, unpatching, and 3.0(quilt)

2012-10-10 Thread Jasmine Hassan
Bernhard R. Link writes: With "3.0 (quilt)" there usually is no unpatching (except if you use some explicit options). So if you need to revert the names, that would be done in the clean target instead. But I really do not see the point of renaming files if you want to stick close to the original

Re: Renaming files, patching, renaming files, unpatching, and 3.0 (quilt)

2012-10-10 Thread Jasmine Hassan
s/origins/urls). Too many to list. On Wed, Oct 10, 2012 at 9:04 AM, Jasmine Hassan wrote: > On Wed, Oct 10, 2012 at 8:49 AM, Raphael Hertzog wrote: >> Hi, >> >> On Wed, 10 Oct 2012, Jasmine Hassan wrote: >>> For instance, I'm packaging Compiz 0.8.8, for MATE des

Re: Renaming files, patching, renaming files, unpatching, and 3.0 (quilt)

2012-10-10 Thread Jasmine Hassan
On Wed, Oct 10, 2012 at 8:49 AM, Raphael Hertzog wrote: > Hi, > > On Wed, 10 Oct 2012, Jasmine Hassan wrote: >> For instance, I'm packaging Compiz 0.8.8, for MATE desktop. This, at >> least initially, requires a lot of code substitutions, and quite a few >> file/d

Re: (un)patching patched files

2012-10-09 Thread Jasmine Hassan
Hi, Has this been reported as a bug yet? The only thing I found to work is: pre_unpatch: [ -f orig.c ] || mv new.c orig.c ... override_dh_clean: pre_unpatch dh_clean # This forces the rename right before dpkg-source --after-build override_dh_builddeb: pre_unpatch

Re: Renaming files, patching, renaming files, unpatching, and 3.0 (quilt)

2012-10-09 Thread Jasmine Hassan
Sorry, the subject should've --obviously-- been "Patching, renaming, ..., renaming, unpatching" On Wed, Oct 10, 2012 at 4:27 AM, Jasmine Hassan wrote: > Dear Mentors, > > I'm surprised this topic hasn't been covered, as I thought it would be > important, at

Renaming files, patching, renaming files, unpatching, and 3.0 (quilt)

2012-10-09 Thread Jasmine Hassan
Dear Mentors, I'm surprised this topic hasn't been covered, as I thought it would be important, at least in some cases. For instance, I'm packaging Compiz 0.8.8, for MATE desktop. This, at least initially, requires a lot of code substitutions, and quite a few file/dir renaming. (ex.: gnome -> mat