On Tue, Feb 15, 2005 at 01:23:06AM -0300, Lucas Wall wrote: > - make dist > - copy the tar.gz to a temp dir with the appropiate .orig Debian name. > - unpack the tar.gz and copy the debian dir into it. > - let dpkg-buildpackage (or similar) compile and generate the diff file, > etc.
Well, that's a bit of magic. If you are in a directory foo-x.y, and run dpkg-buildpackage, it makes a "native" package. If you simply have a foo-x.y.orig sibling directory, it makes a "non-native" package (and concidentally removes the .orig directory). That's wierd. 1) Could someone throw me a bone and point me to the section of the policy or manual where I can read the policy. 2) What other tools exist behind dpkg-buildpackage? I know about debuild, does debuild also produce a non-native package if foo-0.0.orig directory exists? What is the "manual" process for doing it? I always just used fakeroot debian/rules binary to make a deb, and had learned about using debuild to make sure it builds clean. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
