X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Tue, 3 Feb 2015 22:11:12 -0500
Message-Id: <201502040311.t143BCcO018352@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to:
	<CAOFvGD5_w7zqGzNtY5JEN7tgcamcdZt4Z+ZPTjHgr1s7vdTqNQ AT mail DOT gmail DOT com>
	(message from Jason White on Tue, 3 Feb 2015 22:07:11 -0500)
Subject: Re: [geda-user] Footprint Generator
References: <C00DE067-87C2-4F44-B225-2EF53B4C22D9 AT sbcglobal DOT net>
	<mamudg$ou4$1 AT ger DOT gmane DOT org>
	<1345A71A-1F70-4FCD-B738-883EA3C833E5 AT sbcglobal DOT net>
	<marhgq$kkl$1 AT ger DOT gmane DOT org>
	<CAOFvGD7VKhSTFEHHpSTUr4yLzP95=y8nTsx_y7WBnyjfZOXyKA AT mail DOT gmail DOT com>
	<mas0aa$ngv$1 AT ger DOT gmane DOT org> <CAOFvGD5_w7zqGzNtY5JEN7tgcamcdZt4Z+ZPTjHgr1s7vdTqNQ AT mail DOT gmail DOT com>
Reply-To: geda-user AT delorie DOT com


> How nontrivial would it be to add support for a multi line pin where
> the size and clearance of the copper can be defined by layer?

I don't think the problem is 'hard', it's that the problem is
'pervasive' - there are a lot of places in the code that expect pins
and pads to be what they are.  If someone wants to go through the
sources and change all these places (file I/O, screen draws, DRC,
autorouters, optimizer, undo, crosshair, report, exporters, etc), go
for it.