Sorry for the late answer, I was on vacation the last two weeks... On Mon, Aug 06, 2007 at 06:01:24PM +1000, John Pye wrote:

Is there anything that can be done in Build Service to eliminate the redundancy of the package .dsc and debian.control files? Specifically, I have 'Build-Depends' fields in both of these and Build Service seems to be using the package .dsc file to perform the pre-build package installations, but then dpkg-buildpackage (or whatever is used internally) seems to be doing a check using the information in the debian.control file.

My (fairly limited) experience of Debian packaging had led me to believe that the '.dsc' file is normally a resultant file, rather than an input that the user needs to generate. I wonder why Build Service has chosen to use the .dsc file in its implementation?

That's pretty easy to explain: there's no simple way to get the control file data for the build service, it could be in the tarball or somewhere in the diff. Thus we rely on the dsc file. It's true that the dsc file is also created when packages get built, so you can actually use a "dummy" dsc file in the build service that just contains the "Name", "Version" and "Build-Depends" lines. With the newly added "deptransform" script we might also change the code so that the build service looks for a "debian.control" file if it doesn't find a dsc file, but this isn't implemented yet. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org