Ionutz Borcoman wrote: > The original archive is vdk_0_5_1.tar.gz with a top directory VDK-0.5.1. > > The current version of vdk is a developement version and I've decided to > call it: vdk-0.5.1-19990122 (using the release day of the library). > Building the package, I get a tar.gz called vdk-0.5.1.orig.tar.gz. The > top directory of this archive is vdk-0.5.1-19990122. > > Question: > how do I force dpkg-build to create a vdk_0_5_1.orig.tar.gz with a top > directory VDK-0.5.1 ?
Why call it vdk_0_5_1.orig.tar.gz ? Maybe I'm out to lunch here. Here's what I do with packages and seems to me it works: $ mv vdk_0_5_1.tar.gz vdk_0.5.1-19990122.orig.tar.gz $ tar zxvf vdk_0.5.1-19990122.orig.tar.gz $ cd VDK-0.5.1 $ deb-make (or whatever; insert your debian directory) $ dpkg-buildpackage -rfakeroot As I recall, if the debian/changelog file has the version number indicated as 0.5.1-19990122, then dpkg-buildpackage will detect that vdk_0.5.1-19990122.orig.tar.gz already exists and will use it without recreating one. The fact is the tar ball unpacks into something other than vdk-0.5.1-19990122 is not important as long as it unpacks into a single directory. A more experienced developer may correct me. I usually _ask_ questions on this list! Peter <[EMAIL PROTECTED]>
