Re: dpkg --build and empty directories
On Sat, 9 Oct 1999, Bart Schuller wrote:
> On Sat, Oct 09, 1999 at 07:43:15PM +0000, Dale Scheetz wrote:
> > In my rules file, I have the line:
> > install -d /var/log/$(P)
> I hope there's some `pwd`/debian/tmp in front of that path.
Actually, only: debian/tmp/var/log/$(P), which works. The directory
really does end up in the debian/tmp directories, just doesn't appear in
> > After the build process, debian/tmp contains the path /var/log/dssb, as
> > expected, but the contents of the .deb file has no such directory.
> > If, on the other hand, I touch /var/log/dssb/.keepme, the directories get
> > installed into the package file.
> > I use no helper scripts, so I have no idea just what problem you are
> > referring to, but it doesn't seem related to the one I see.
> It's not related (and a bad joke).
> I just tried the simplest test I could (but still using debhelper):
> - created empty directory test-1.0
> - ran dh_make
> - replaced "$(MAKE) install" with "install -d `pwd`/debian/tmp/var/log/blah"
> in the "install" target
> - ran "fakeroot debian/rules binary"
> Which did work. (the deb contained all directories leading up to my
I wonder if this might be a problem with Midnigh Commander.
I use mc to look inside .deb files. (just hit enter with the highlight bar
over the filename, and ... grind, grind, and you see the inside of the
package file like it were another file system)
Is it possible that the tar command mc is using fails to present any empty
directories? (I guess I'll have to devise an experiment.)
> The relevant call to dpkg was: dpkg --build debian/tmp ..
Absolutely the same here...
_-_-_-_-_- Author of "The Debian Linux User's Guide" _-_-_-_-_-_-
aka Dale Scheetz Phone: 1 (850) 656-9769
Flexible Software 11000 McCrackin Road
e-mail: firstname.lastname@example.org Tallahassee, FL 32308
_-_-_-_-_-_- See www.linuxpress.com for more details _-_-_-_-_-_-_-