أحمد المحمودي wrote: > My case is like this, I got an upstream tarball with 2 subdirs, > each subdir has its setup.py, and each of those subdirs should be > installed in a separate binary package. > > So, in debian/rules I would do: > > override_dh_auto_install: > dh_auto_install --sourcedirectory <dir1> -p<package1> > dh_auto_install --sourcedirectory <dir2> -p<package2> > > and I would expect that this would install in debian/<packageN>, but > instead dh_auto_install ignores the -p<packageN> switch, and just > installs to debian/tmp
The reason dh_auto_install installs to debian/tmp is so that dh_install can then be configured to copy files from there into debian/<package>. Which is useful if you need to move files to different directories, or if not all the files should be included, or of course, if the files are split up into several binary packages. So I don't think that making dh_auto_install behave as you request is a good idea, because having it install directly into debian/<package> would eliminate the ability to handle any of those three cases via dh_install configuration. Anyway, you have several other options: * override dh_auto_install and run make install by hand in the two source directories. * override dh_auto_install to do nothing, and configure dh_install something like this, so it installs directly from the source directories: debian/package1.install: dir1/foo usr/bin debian/package2.install: dir2/bar usr/bin * let dh_auto_install install to debian/tmp and configure dh_install to split things from there into the two binary packages. (Unless there are filename conflicts.) -- see shy jo
signature.asc
Description: Digital signature
