r4762 - packages/trunk/allacrost/debian

[Gerfried Fuchs]

* Stefan Potyra <stefan.potyra at informatik.uni-erlangen.de> [2007-12-18 18:10:27 CET]:
> Hi,
> 
> Am Dienstag, 18. Dezember 2007 18:04 schrieb Gerfried Fuchs:
> >  I wonder - even if it's easy to readd quilt and the likes, should we
> > really do this? I mean, add quilt when needed, remove it again when last
> > patch is gone just to readd it again when the next patch will come it
> > (which quite propable will)? I don't consider the overhead on the
> > buildds to be that high if we just leave it in there, is it? I am a bit
> > more concerend about removing and adding the same things again and again
> > over the times, having places to fumble agaiin and again with certain
> > bits...
> >
> >  Just a thought, would like to see the input of others, too.
> > Rhonda
> 
> Hm... will quilt/dpatch make problems, if there is no patches directory (as 
> you can't store empty directories in a .diff.gz)?

 Nothing a quick check couldn't help:

#v+
$> rm -r debian/patches
$> debuild -uc -us
[...]
$> echo $?
0
$> grep patch ../*.build
$ grep patch ../*.build
QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null pop -a -R || test $? = 2 
No patch removed
rm -rf .pc debian/stamp-patched
QUILT_PATCHES=debian/patches quilt --quiltrc /dev/null push -a || test $? = 2
No patches in series
touch debian/stamp-patched
#v-

 I would be pretty surprised if dpatch behaves silly in that respect.
Rhonda