Johannes Schauer Marin Rodrigues <jo...@debian.org> writes: > I fear I do not quite understand what kind of feature you are asking for. Do > you really think it would be a good idea if sbuild, every time you run it, > first locates a .dsc, unpacks the .dsc, compares the unpacked .dsc to your > current directory and only invokes the clean target if it finds differences? > Would there not almost always be differences because you only invoke sbuild > *after* you've made some changes to the unpacked source directory? And what > should sbuild do if it has detected changes? It would still need to run the > clean target before it can create the new source package. > >> Other than that, can we run "dh clean" inside the chroot? > > What would that accomplish? At the point where the .dsc is unpacked > inside the chroot, it already is clean. You need a clean unpacked > source directory, so that you can build a .dsc so that it can be > copied into the chroot. So this cleaning has to happen on the outside.
Those questions are all valid, of course, if you think of the .dsc as the input to sbuild. Up until today I was not even aware that this is how it works. The feature I'm asking for is that on a brand-new Debian install I think I should be able to 1. apt install sbuild 2. create schroot for sbuild in whatever way 3. apt source package 4. cd package 5. sbuild Today this doesn't always work, because sbuild wants to "dh clean" outside the chroot. Omitting the "dh clean" (by relying on dpkg complaining) would be one way to get this working. Doing the "dh clean" inside the chroot after the Build-Depends have been installed is another. Maybe the above sequence shouldn't be expected to work, but that makes sbuild less useful in my view. I can make --no-clean the default in my config, I suppose. Probably others use sbuild in this way too? I guess I have no way of knowing.
