X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=date:from:to:subject:message-id:references:mime-version
         :content-type:content-disposition:in-reply-to:user-agent;
        bh=iKqKUiI2CyTl1iAwxI8+cgXINglCSCg2L2RYm9wJ/oo=;
        b=R7Dhz3Z8cm4FCXA4xgYLZXJq70q9H/WGuyg12KQN9x6mwSfzAUAQMBitD9GJHZULGS
         RQb5eRQg6FrrkbUVE7Jo3HLO0tL/yKT2st4scoz8lPoNccru63HH9/0O4NUFve7pAd3S
         f15aj4PkMlJPqH3Uccfh4Gy+oDAXB6sUyFOro=
Date: Tue, 8 Nov 2011 20:47:34 +0100
From: Cyril Hrubis <metan DOT lists AT gmail DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] duplicate refdes values
Message-ID: <20111108194734.GG6940@yumi>
References: <20111108100616 DOT GA32119 AT yumi>
 <89AF1CB2-6703-4ABC-A43D-7EA37559426F AT noqsi DOT com>
 <20111108091933 DOT 66b26424 AT svelte>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20111108091933.66b26424@svelte>
User-Agent: Mutt/1.5.21 (2010-09-15)
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

Hi!
> > > I've got bitten by this once more and decided for fix. The
> > > problem is that I've, by a mistake, forgot to change refdes on
> > > one of my resistors and spend another ten minutes by figuring
> > > out what went wrong.
> > > 
> > > What I want to fix is that both gsch2pcb and pcb are silent
> > > about this and the pcb just picks up only one of them.
> >...
> > 3. The drc2 back end to gnetlist already complains about
> > duplicated refdes values for non-slotted components. Checking a
> > design for errors is what drc2 is for, and if you're not using
> > multiple heterogeneous symbols for parts, drc2 will do what you
> > want here. The problem is that this isn't necessarily an error:
> > this is one of the many cases where drc2's model of design is
> > narrower than the capabilities of the toolkit. In this case, it
> > is hard to fix drc2, as the indications of true error
> > (inconsistent pin connections) are hidden behind the
> > unnecessarily opaque gnetlist back-end API.
> 
> Agreed, the drc2 backend has caught my copy-and-pasting symbols
> without changing the refdes many times.  I always run my drc script
> after making schematic changes.  It might be a good idea for users
> to include a drc2 run in the script that runs gsch2pcb (Makefile,
> shell script, whatever).

Ah, found it.

Hmm maybe it could be easily used from gsch2pcb automatically to check
for some of the problems.

-- 
Cyril Hrubis