On Sun, 2006-05-14 at 11:47 +0200, Wouter Verhelst wrote: > On Sun, May 14, 2006 at 10:00:25AM +0200, Ondrej Sury wrote: > > On Sat, 2006-05-13 at 14:54 -0400, Eric Cooper wrote: > > > Is there a way to tell deborphan to follow the build-dependencies > > > of a set of source packages? I know about deborphan's keep file, > > > but that's too tedious to keep up-to-date by hand. > > > Is there another tool I should be using? > > > > Yes, don't clutter your system, because it will end in sorrow :-). > > Your system will have mix of your local packages and at the end of the > > day you will build package which will be: > > > > a) unbuildable > > b) uninstallable > > > > Right solution is to use pbuilder, which will: > > > > a) always ensure that package can be built using unstable > > b) keep your build environment clean > > c) keep your local system clean > d) take much longer to build your package; the exact factor depends on > the size of the package, but a factor 3 isn't too uncommon for > smaller packages, which isn't very interesting in cases where you > need to do a lot of work on a given package.
I usually solve this by doing: pbuilder login and work inside pbuilder environment until I got the package in right shape, then sync it with outside, exit out of pbuilder and build final version in clean pbuilder. There is a work on COW support, which could eliminate that time, cpu and io consuming tgz unpack at start... > pbuilder is a wonderful answer to the question of "did I get my > build-dependencies right?", but it's not a magical wand to solve every > problem, and certainly not to solve the problem of "how do I keep the > number of -dev packages on my system under control?". It does solve this problem in it's own way, because you don't have to have any -dev package installed at all in your base system... But sure, it's not magical wand and it helps anybody to keep their package in better shape. Ondrej. -- Ondrej Sury <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
