Dave, I have alternate suggestions for both situations you mention.
First, there is a big project by some of us to rescue the remaining 300-400 packages which never moved from 10.2 to 10.3. Ben Hines set up this nice comparison chart at http://fink.sourceforge.net/pdb/compare.php which all fink developers are welcome to modify. (You change the colors via checkboxes, and the button at the bottom of the page.) If you are aware of problems with some of your packages, you can just mark them red or green and then other folks won't touch them. Second, when I am working on a new binary distribution (as I am now), I frequently discover the need to add BuildDepends. This is a large task, and what I am doing is getting documented in fink-commits; I am not too receptive to the idea that I would need to send separate emails to maintainers when I do this. Maybe some day we'll have a better way to test these things, but at the moment it's only when following the bindist script that removes absoletely every non-essential package before it starts to compile the one you want, that these missing BuildDepends are detected. So there are quite a few; it's a big job; and I don't want to make it bigger. So I guess my suggestion for the second problem would be: when you are going to revise one of your packages, you should probably start with the CVS current version rather than a local copy. -- Dave ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
