On Sun, May 30, 2004 at 11:33:20AM -0400, David R. Morrison wrote: > Dear Fink developers, > > For some time, I've wanted to have a way to validate that packages are > using the BuildDependsOnly field correctly. The test I want to employ > is this: if the package installs anything into /sw/include, it should > be declaring BuildDependsOnly to be true. (This doesn't guarantee that > the dylib symlinks have been put into the correct place, but it does > guard against someone overlooking the need to declare BuildDependsOnly > in a -dev splitoff.) > > Now this is a bit tricky: we need to do the validation on the .deb file > in order to see if anything was installed into /sw/include, but the > BuildDependsOnly declaration is in the .info file. And there is no way > to track which .info file was used to create a .deb file.
Debian Packaging Manual 5.7 "User-defined fields" (though as I read it is self-contradictory), suggests we could maybe pass the BDO flag in the control file? If so, that would certainly be a cleaner solution than: > For each package, at build time I'll touch one of the following two files > (after creating the appropriate directory): > /sw/share/BuildDependsOnly/true/%n > or > /sw/share/BuildDependsOnly/false/%n dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
