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=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=X/E0qAf65L6zT4WVVFjNhGQpdS+UAdW/OAy0ziToAAw=;
        b=CdHBVxWkvmhfP8FYpQ7v4VmZuN7145TKXN+KBmWXMrWsS38oU44Me5O2PwamBgHNpc
         qEFSK8Tv9dXQ3R7PV5Da8w7iEMT4uDLOugvUcryA1HJiltenLxYM0GiWhbOkoPoOH7c3
         dEoqILWnmnxLHxrewYiKFyMDKCr0D7o42VpLbVCqq0cxRnZyhCa8Cfo+issvY7BlFMNt
         5la5/G2EpTjdoXB9NQ1GUmELFmVRHihXnM5p39LSPW6G458lZ9K/cVaaFPc9HdJSMIHg
         RAwy/O4VCNNOXznmmBFgvwP7TgkLYAECSxqTbA+t4/IdbGUE/l22a1X4hJ7mCw2+l6GK
         MXew==
MIME-Version: 1.0
X-Received: by 10.50.230.19 with SMTP id su19mr33447851igc.41.1394683959700;
 Wed, 12 Mar 2014 21:12:39 -0700 (PDT)
In-Reply-To: <CAOP4iL2JsFk6qDLLiuAZHShu1ben0KPs+k_GKP-fPQKuQf-C6w@mail.gmail.com>
References: <CAG4ve9LgHNoVZoGaGgF67tadJ_n=L6Uy1g=UPPrkM0fL6Rgufw AT mail DOT gmail DOT com>
	<20140127234944 DOT 924148045B78 AT turkos DOT aspodata DOT se>
	<CAG4ve9+3jhFJ1Cr6CLUyLX_y02uigJECiUCwxjUWdP=heVocqg AT mail DOT gmail DOT com>
	<20140128201110 DOT DF7D78045B78 AT turkos DOT aspodata DOT se>
	<20140129072550 DOT GA24560 AT localhost DOT localdomain>
	<CAG4ve9+v9QxNRaPSFkmGfr6bKsv7km-Gt_gwXF7Eh4TX+AmNug AT mail DOT gmail DOT com>
	<CAOP4iL2JBUdF93kZF-iQ9Rv+VTN3iXoT+6C4LoBi5qaMxof=sA AT mail DOT gmail DOT com>
	<CAG4ve9+QsUf=nVXPe-f3VddGiqHn8sjZUJNkdu3QV1cOQDWiAg AT mail DOT gmail DOT com>
	<20140309173951 DOT 738798020179 AT turkos DOT aspodata DOT se>
	<531CF3BE DOT 8070407 AT ecosensory DOT com>
	<CAG4ve9LKJS1RxPZxUdOSwFifQXoVJtJMOV=7PMs2vrjf70L1KQ AT mail DOT gmail DOT com>
	<CAOP4iL3mQJjH_2gOZ1E=POzpiLuJKTxOu_FN7UD-=BfV6BOQ1w AT mail DOT gmail DOT com>
	<CAG4ve9L-HKjGH3SZ4UFHfQPonkvxJbGoqpnQnxAmcurNaFuRaQ AT mail DOT gmail DOT com>
	<CAOP4iL1d0WQ5x65NfiXoR3uHGP8Hm8uUKS8n_gWSGsFrY6JSMA AT mail DOT gmail DOT com>
	<20140311164227 DOT D853D8020170 AT turkos DOT aspodata DOT se>
	<CAG4ve9+2bfaoZYSTKgfWNTQ=GtDZ+wQeioiqstVEK2yhp=Y=Tg AT mail DOT gmail DOT com>
	<CAC4O8c8ySdBMRRYVZY7MaDhSpGSwqwcUsjY4xdWMKPdTRL-NEA AT mail DOT gmail DOT com>
	<20140312121641 DOT 9E8738020170 AT turkos DOT aspodata DOT se>
	<CAC4O8c8=tCXae2TGwZizmcacpnLwtLsG4=6NbvOFVqvyeJQHfQ AT mail DOT gmail DOT com>
	<CAOP4iL2JsFk6qDLLiuAZHShu1ben0KPs+k_GKP-fPQKuQf-C6w AT mail DOT gmail DOT com>
Date: Wed, 12 Mar 2014 21:12:39 -0700
Message-ID: <CAC4O8c_nSZjqTVeF2CQpmuLVewGq6nNpvsmk8UEC-MmOf2j9sg@mail.gmail.com>
Subject: Re: [geda-user] identical symbol names
From: Britton Kerin <britton DOT kerin AT gmail DOT com>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=ISO-8859-1
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

On Wed, Mar 12, 2014 at 5:35 PM, Ouabache Designworks
<z3qmtr45 AT gmail DOT com> wrote:
>>
>> Someone a while back was talking about how schematics would be more
>> portable
>> if they came with an in-file-lib, this would apply to subcircuit
>> schematics
>> as well I would think.  Its not the only thing you need for distributable
>> modules of course but its one piece.
>>
>> Britton
>
> So your boss gives you three designs with in-file-libs and tells you to
> consolidate  them into
> one design. If they all use the same common sub-circuits that have been
> slightly tweaked
> in each design then you have a real mess on your hands.  This is common in
> ic design.

True.  But the subcircs may have forked for valid reasons, in which case
you have design work to do if you want to consolidate them no matter how
they've been stored.

Also, at the moment gEDA doesn't have any subcircuit repository of any sort,
so you *always* get to redesign (or reenter) everything.  That's worse than
sometimes having to because of gratuitous forks.

In my experience even very large projects have trouble getting their external
libs set up in a truly standard way st they can be used without hassle.
Like the original poster I doubt gEDA will manage it, so I'd like to see
the easier alternative happen.

Britton