On Fri, Oct 29, 1999 at 08:27:01AM -0400, Ben Collins wrote: > > The problem comes for the actual maintainer who wishes to update the > source deps (and doesn't always use a .dsc, since he is just building a > new package). The Build-* stuff should come from the debian/control file > /after the package is built, but before the source tree is cleaned/.
I think I am confused. About which situaton are we talking now? Maybe there are two cases we consider: 1. A user gets a source package and wants to check the dependencies after unpacking but before compiling. 2. A maintainer builds a package, and wants to get the source deps into the dsc file. In the first case, the *.dsc file is quite sufficient. You just have to keep it around. The "random files cluttering up the dirs" is not justified, IMHO, as the alternative (copying the information somewhere in the build directory) is not more appealing to me: It seems to be more obscure and overly complicated, and unnecessary as the information is there in a well defined place: If you choose to ignore it and delete the file (or not copying it in the first place), you declare that you checked the depends and don't need them anymore. This is different from what you seem to mean above, in which case there doesn't necessarily exists a dsc file, and it should not be used. Instead, the information should come from the control file. To support autogeneration, the information should be considered to be complete only after the package build. Is this what you mean? Thanks, Marcus -- "The purpose of Free Software is Free Software. The End and the Means are the same." -- Craig Sanders Marcus Brinkmann <[EMAIL PROTECTED]>
