On Fri, Nov 14, 2003 at 01:54:51PM +0000, Julian Gilbey wrote: > In response to Branden's question (does debian/control already have to > exist when the package is unpacked), I would suggest the following: > > Before debian/rules build* is run, one has to check the > build-dependencies. So at this point, at least the source section of > debian/control must exist. Acknowledged. I don't think there's anything wrong with requiring people who want to generate debian/control to make their build targets depend on debian/control. This doesn't make *unpacking* depend on the presence of debian/control. > And since this field (whatever form it eventually takes) would exist > in the source section of debian/control, and would not be needed until > after the build-dependencies are checked, there should be no problem. > > And then again, we can always use debian/interfaces or > debian/rules.targets or something similar instead.... I really like the debian/interfaces proposal. -- G. Branden Robinson | The errors of great men are Debian GNU/Linux | venerable because they are more branden@debian.org | fruitful than the truths of little http://people.debian.org/~branden/ | men. -- Friedrich Nietzsche
Attachment:
signature.asc
Description: Digital signature