X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Wed, 23 Jul 2014 06:11:01 +0200 (CEST)
X-X-Sender:	igor2 AT igor2priv
To:	geda-user AT delorie DOT com
X-Debug:	to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From:	gedau AT igor2 DOT repo DOT hu
Subject:	Re: [geda-user] Eagle .dru file definitions, anyone?
In-Reply-To:	<53CF33CA.802@sonic.net>
Message-ID:	<alpine.DEB.2.00.1407230610230.6734@igor2priv>
References:	<53CF33CA DOT 802 AT sonic DOT net>
User-Agent:	Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version:	1.0
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

On Tue, 22 Jul 2014, Dave Curtis wrote:

> Has anyone seen a description of the Eagle .dru (design rule) file?
>
> I notice that a lot of fab houses publish Eagle .dru files for their process, 
> and it might be a quick/easy project to create a .dru to PCB design rule 
> translator for most of the common/meaningful rules.
>
> It's a plain text file with a bunch of names and values, so it wouldn't 
> exactly be rocket science to reverse engineer, but I thought someone might 
> have run across a document on it.  I haven't been able to snag anything with 
> Google.

If it's that simple, we could write a script that creates/replaces the DRC 
part of a pcb save. Could you attach some examples?

- Raw text -