Package: debhelper
Version: 7.0.17
Hello,
Today I tried to convert a simple rules file to use "dh". All went
relatively smoothly, but I noticed that I couldn't run `debian/rules
install` after adjusting eg. debian/docs: it did nothing.
I figured out it did nothing because of debian/pkg.debhelper.log:
debhelper thought it had already done all the necessary steps. So I went
ahead and removed this file, but then `dh install` wanted to build the
package again (because it thought it hadn't been built, ttbomk).
I managed to obtain the behavior I wanted with:
install: build
dh install --after dh_auto_test
but I find this a bit non-obvious for such a (I believe) common
operation. Is this the way it's supposed to work, or can usability of dh
improve in this regard?
If make dependencies already ensure build must have completed
successfully before install, why must dh enforce it as well?
Thanks for considering,
--
Adeodato Simó dato at net.com.org.es
Debian Developer adeodato at debian.org
Truth is the most valuable thing we have, so let's economize it.
-- Mark Twain
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
