> > That's why we tell people to use pbuilder. > I think I disagree with the reason given for this advice. What > is the end goal that we are trying to achieve? Is it to upload binary > packages that build despite leaving flaws i the build process? Always > building in pbuilder masks errors like the $TAPE error; we would have > been better off having the build fail and be corrected.
Why should we force 7000+ source packages clean their environment when debuild/pbuilder/sbuild etc will do that anyway? Worse, it's not even trivial to clean environment in a Makefile. Howabout documenting it as a fact that debian packages should be built in sanitized environment. > Me, I would try to build in pbuilder while I am trying to figure > out what the build dependencies are, and periodically on new upstream > to ensure the build dependencies have not shifted, but other times I > would build and test on my own machine, to more closely replicate the > environment that downstream users might have. As Dato already said, using debuild is enough. -- "rm -rf" only sounds scary if you don't have backups -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
