@DiodeDave It is not that I want the path clipped but rather that a lot of users of Fritzing are makers and a lot of makers do home etching and they want a nice round hole in the SVG and/or PDF output to center their drill. For those cases we should be doing a difference of the drill SVG from the Copper SVG giving them exactly what they want.
As for the gerber output it is good to hear that solid disks are preferable to rings. But the reason for the rings is how Fritzing works for parts creation. We create an SVG image with rings and Fritzing calculates the hole diameter you want from the SVG and then uses the SVG image as the copper component. It should not be hard to discard the inner SVG data for the rings to create a solid but again that would require someone more familiar with Object Oriented Programming than me.
The actual bug here is the result of the math being done inside a function and the same math being done to the data before sending it to the function. So my patch was to simply remove the math being done before the function and just leaving it in the function itself.
As for netlists we can currently export them in XML and SPICE but I do not know the compliance ratings for them.
@5volts I have reverted the changes making the current development version unusable and created a branch for it https://github.com/Intrinsically-Sublime/fritzing-app/tree/Testing it has the patch for this issue plus all the other small bug fixes that have been committed in the last year but without the bug that has been preventing a new version. You will still need to compile it yourself unless you are a Linux user in which case let me know and I can share the 64bit Linux Binary.