> Frank Küster <fr...@debian.org> writes: > > Maybe some other tool "usually" also creates DEBIAN, but not in my case? > > I'm really confused by this too, since the calling sequence for a binary > build also runs dh_makeshlibs before running dh_installdeb, > dh_makeshlibs seems to assume that the DEBIAN directory already exists > (I can't find a mkdir anywhere and it writes to the shlibs file there), > and I can't figure out where earlier in the calling sequence the DEBIAN > directory would be made. > > Clearly I'm missing something....
dh sequencer also calls dh_installdebconf earlier in the call sequence (which Frank's rules was actually missing), which takes care to create debian/pkg/DEBIAN/ directory. So, when dh_makeshlibs and dh_shlibdeps enter the scene, we have valid package directories, as far as dpkg-shlibdeps is concerned. -- pub 4096R/0E4BD0AB 2003-03-18 <people.fccf.net/danchev/key pgp.mit.edu> -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
