Fabian Greffrath wrote: > My propose is to introduce another set of options to the "dh" command, > namely --configure-dir and --build-dir which can be used to point to > the directories containing the configure script and the Makefile and > which would default to "./" if unset.
In the buildsystems branch in git, there is support for a --builddirectory, but this is used in the more common case of specifying a directory that the toplevel configure and make should be run from, and which is deleted on clean. I suppose you could get the behavior you want out of that if dh_auto_clean could be prevented from removing the directory. However, the case you describe certianly seems unusual; we expect to have a toplevel Makefile, and it seems entirely appropriate for the packaging to add one if upstream for whatever reason left it out. That to me seems a better solution than adding more dh_auto_* switches for such an unusual case. BTW, Modestas, it looks like makefile.pm does not call mkdir_builddir to create the builddir before using it? -- see shy jo
signature.asc
Description: Digital signature
