Hello, On 2009 m. May 26 d., Tuesday 21:28:57 you wrote: > 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.
What the reporter is asking here is a way to tell dh where the source directory is. He basically wants dh to chdir to that directory before executing any build commands and to assume all files which are supposed to live in the source directory can live somewhere else but the top level dir. I think it is a reasonable request, it has a couple of use cases and could be pretty easily implemented on top of current buildsystems branch and I'd be willing to do that (probably for 7.3.1). So basically it is a wish for $ dh -- source-directory option. Build directory is a bit different beast. The whole point of it is to support building outside source tree, not inside it. If configure script is in the build directory, it is effectively in-source building (at least from autoconf POV), just now the source directory is somewhere else but top level dir as far as dh is concerned. However, I still have to finish docs for current stuff (I'm better at writing code than docs, really) :D I'm really sorry for long delays, hopefully I'll finish soon. > BTW, Modestas, it looks like makefile.pm does not call mkdir_builddir to > create the builddir before using it? makefile.pm does not have "configure" support (on purpose) and it actually depends on Makefile existance in the build directory. Its derivatives create builddir at "configure" stage as needed (if needed). So Makefiles are supposed to be created in the builddir while configuring or they already should exist there for plain makefile.pm to be usable. -- Modestas Vainius <[email protected]>
signature.asc
Description: This is a digitally signed message part.
