On 12/27/2011 12:47 AM, Jonathan Marsden wrote: > I'd be wary of removing the dh-autoconf usage, but it's your call. > dh-autoconf is in the lucid-backports repository, so as long as the PPA > is set to use it, and your local pbuilder for lucid is also set to use > it, there should be no issue using dh-autoreconf for Lucid builds.
So far removing the dependency on dh-autoconf provided me with a few good presents. It patched a number of autoconf/automake files that were outdated. From the patches I could then update the source packages. This involves files INSTALL, missing, mkinstalldirs, install-sh, and perhaps a few more I didn't write down all updates. >From what I gather, the dh-autoconf package makes the debian patch files smaller in the majority of the cases by removing some updated files that the debuilder scripts generated. But since I patch the source at the same time, there was no problem with bigger patch files, and, the good part, the upstream source gets updated. > > I think this means I am now no longer in the bibledit-gtk packaging > business at all, you can take it from here :) Well, your absence from the bibledit-gtk packaging will be felt indeed. If you opt to be out of that business, may I thank you for the years you ensured that the packages got updated. And may I also declare my intention to probably talk to you in case I am stuck. Teus. _______________________________________________ Pkg-crosswire-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel
