Stefan Potyra wrote: >> If you verify that the clean rule restores the build directory to the >> exact state it was in before building, then the package will build >> cleanly a second time. > > not quite, at leat from a practical POV: > If I run make -f debian/clean, I want the package to be in a state to build > again when runing make -f debian/rules binary. And I don't want the .diff.gz > list any remains of failed attempts to modfify the package. > > from that practial POV I'm not really interested in if a package decides to > remove files on clean that can/will be recreated during build, e.g. > Makefile(s) create from Makefile.am(s).
If the clean rule removes such files, then they should not be found in the package to begin with. IOW, the clean rule should be run before building the source package, so a clean following a build should return the working directory to the exact same state. If it doesn't, that may not prevent the package from building a second time ( then again, it might, or might cause it to behave differently when built ), but is still undesirable. -- Ubuntu-motu mailing list Ubuntu-motu@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
