On Mon, Jul 24, 2000 at 04:23:22PM -0400, Matt Zimmerman wrote: > On Mon, Jul 24, 2000 at 03:17:55PM +0200, Adrian Bunk wrote: > > > I'm looking for an easy way of getting the build dependencies of a > > package. At the moment I do look through the build log manually, and if I > > oversee something Roman Hodek sends a bug report that the m68k > > autobuilder found some missing build dependencies. Is there a more > > comfortable way to get the build dependencies of a package? Or how does > > the m68k autobuilder find them? > > Joey Hess wrote a handy mini-tutorial on this in > <[EMAIL PROTECTED]>. A copy is attached. Err...a copy is attached. -- - mdz
I figured this might save some people some time. If you want to set up a small debian install to see if your build dependancies work in the real world, or to find out what build deps your package needs in the first place, just type the following: mkdir /tmp/debian cd /tmp/debian tar zxf <mirror>/debian/dists/unstable/main/disks-i386/current/base2_2.tgz cp /etc/apt/sources.list etc/apt/ cp /etc/resolv.conf etc/ chroot `pwd` bin/sh apt-get update dpkg --purge lilo yes '' | apt-get -y install build-essential Then you can go archive the resulting directory tree, and use a fresh copy to test-build each of your packages in. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
