Bug#490935: pbuilder: Impement to ensure that clean after build is working
Loïc Minier
lool at dooz.org
Tue Jul 15 21:49:01 UTC 2008
Hey,
On Tue, Jul 15, 2008, Carl Fürstenberg wrote:
> Per http://release.debian.org/lenny/goals.txt a release goal is double
> compilation support, and one step to ensure that is to verify that clean
> works. When doing an normal dpkg-buildpackage, you can pass the
> parameter -tc to clean the directory after build, but when building
> under a pbuild environment, no such posibillity exists (Probably because
> of the reasoning as it will be deleted anyway, so no clean is required).
You mean passing "--debbuildopts -tc" doesn't work?
> But though Policy section 4.9 specifies that clean must be able to restore,
> many developers miss to check clean after build as they often build in
> pbuilder environments, and the only way to check that is to do an normal
> build, which might miss other things instead.
>
> Even trhough it will take some CPU cycles more, my advice is to clean
> in the chroot by default.
I don't think pbuilder needs to divert from dpkg-buildpackage here;
just like nothing runs lintian by default, some configuration is needed
for stricter QA with pbuilder. I think that's fine, but perhaps we
could offer a "paranoiac" or "strict" or "qa" pbuilder config which
would enable lintian, clean after build etc. I think this is more
something wishlist / nice to have than a defect in pbuilder though -- I
do understand why you want to use the lever though.
Bye,
--
Loïc Minier
More information about the Pbuilder-maint
mailing list