X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Message-ID: <53CFCB9F.2050802@sonic.net>
Date: Wed, 23 Jul 2014 07:50:07 -0700
From: Dave Curtis <davecurtis AT sonic DOT net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121028 Thunderbird/16.0.2
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Eagle .dru file definitions, anyone?
References: <53CF33CA DOT 802 AT sonic DOT net> <alpine DOT DEB DOT 2 DOT 00 DOT 1407230610230 DOT 6734 AT igor2priv>
In-Reply-To: <alpine.DEB.2.00.1407230610230.6734@igor2priv>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVbbuVPKfnCSMHBtXfIqqYuayYd3dMQNNSxwOjfNjm03NARZ+c3RngiY9YrHDr+Sb3SkcP8kz3cllJJOpvWGaLcBscn7w1r3Zgg=
X-Sonic-ID: C;gAt5o3gS5BGbn/I5oK8kYw== M;BgK2o3gS5BGbn/I5oK8kYw==
X-Spam-Flag: No
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Reply-To: geda-user AT delorie DOT com

On 07/22/2014 09:11 PM, gedau AT igor2 DOT repo DOT hu wrote:
>
>
> 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?
>

oshpark publishes their rules here:
https://oshpark.com/LaenPCBOrder.dru

if you google for 'dru' you get more hits of fab house dru files than 
about anything else.

I don't really think it makes sense to modify the drc part of PCB's 
save, as the two sets of design rule specs probably don't line up really 
well. But maybe a "load rules from dru file" menu selection would be 
good -- it could read a .dru file and pick out the pieces that make 
sense, then just go forward with PCB in the normal way.