I gave this a lot of thoughts lately. The solution I found was to convert the LaTeX documentation to another one, less demanding on build-deps. I was thinking of POD format, for example.
Then, I went to upstream explaining the circular build-dependency problem
and asking whether they would accept a patch doing this documentation format
convertion. The answer was a plain /no/ (actually, a bunch of them ;)
Their argumentation is that the whole quilt infrastructure should not be
used as a build dep. After all, once you're done with hacking, the only
thing you have to do to build the package is to use:
for patch in `cat debian/patches/series|sed 's/#.*$//'` ; do
patch < debian/patches/$patch
done
No need for the whole infrastructure indeed.
So, I decided to add a new quilt-build-dep package providing a simple script
able to add all the patches (and remove all of them for the clean target)
provided that they were not modified and that they do apply cleanly. This
package would be very small and arch: all. I could call it quilt4autobuild
or so to make its purpose clear.
The existing quilt package would be made Replaces and Provides
quilt-build-dep, and I think we would be set, wouldn't we?
Clint, I am interested in your advice before I start hacking on this.
Bye, Mt.
--
use Mail::Signature;
$sig = Mail::Signature->new;
print $sig->random;
signature.asc
Description: Digital signature
