X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Thu, 22 Oct 2015 12:50:09 -0400
Message-Id: <201510221650.t9MGo9YB003639@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <20151022161821.637d558cf569135120a20682@gmail.com>
	(geda-user AT delorie DOT com)
Subject: Re: [geda-user] A lesson from gnet-makefile
References: <DA7D969B-6516-4633-831C-FFADA38E1807 AT noqsi DOT com>
	<CAM2RGhRN5S1KZCNFQwoVTPg3=mC5xrK2z9XTOpWwPuF0iVS+Rg AT mail DOT gmail DOT com>
	<73ED29DA-968B-4675-9B00-125E03683C9B AT noqsi DOT com>
	<CAM2RGhSvpVvboJ-gdyrojAzggFEBnAr30CKNQBefjci-PA1n6g AT mail DOT gmail DOT com>
	<201510220112 DOT t9M1Ccfq013731 AT envy DOT delorie DOT com>
	<CAM2RGhQhNkShqtN8uyCSd7R+V4FgLXDZTvTC2RTdmKF7C_8ndA AT mail DOT gmail DOT com>
	<201510220136 DOT t9M1a5Uw015222 AT envy DOT delorie DOT com>
	<CAM2RGhQOpnBXbZXngNq=RcQTZN=UrU+PGzTZ9AC=xKNfu_zQkQ AT mail DOT gmail DOT com>
	<201510220149 DOT t9M1nrIe016145 AT envy DOT delorie DOT com>
	<CAM2RGhQ26+gpcAeTdgJpBEh0egOGLYcpizQ+B6kfTQLowEk5xQ AT mail DOT gmail DOT com>
	<20151022023002 DOT GA25952 AT recycle DOT lbl DOT gov>
	<20151022090751 DOT ecb5bc25c7d968646dea2e85 AT gmail DOT com>
	<n0ad7l$79l$1 AT ger DOT gmane DOT org>
	<CAM2RGhTP3qaMMDK0BrAZdFFrtZyNeTc90TJ9SSQ0wx1DK_RyEw AT mail DOT gmail DOT com> <20151022161821 DOT 637d558cf569135120a20682 AT gmail DOT com>
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> According to my oppinion ideally DRC should look on copper layer not
> which symbol it belong to. If it look on nets only I guess it could
> more or less temporary assign some net to all copper objects.

DRC works kinda funny.  First, it generates a connectivity list based
on the copper the way it is (and it looks at copper, not nets - this
includes all vias, pins, pads, polygons, lines, arcs, etc.).  This is
the "base" netlist (not the same as the "desired"/imported netlist).

Now, it "bloats" everything by pretending the sizes are increased by
some amount, and recomputes the netlist.  If the new netlist differs
from the base one, you have a minimum spacing issue.

Now, it "shrinks" everything, and repeats.  Changes indicate a line
width minimum issue.