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:content-transfer-encoding;
        bh=yy6QhX0SpELxmHGeg5f22olqYqVIaoWhm4eR8puhUzU=;
        b=XayrocxRlNisg/pUdTIpj0RS5EnpRXlIG5oflO/H6b2TInSKKQ2E+UyozSJUP5L5P9
         il3rzvqCU5pniyLWF/EaYqe3XU3GAbl/gi31iEnJiiPB5ZqokExVIaiIfS2+zLrNUowP
         cuzAIjCLQ+bFEGxhqLz5fxI7T/uk6ftrpM5qiOqXkYq8sZEgn37DZQD8Qyp9FzgJACBK
         0GErjZexorVjGV7O9hAeoCkQ1qfGS/Yn2TyVgOpjCtolYPk3FvMBPz7SyQaxPQowoP+5
         k3k//wsts6XXKXAAqFq2B5JwdGfDuVAgqRUpzhcLOaoPo/j7rLMC0SM77ZlTRMc4omiK
         l9Pw==
MIME-Version: 1.0
X-Received: by 10.50.225.134 with SMTP id rk6mr26779529igc.31.1394575689304;
 Tue, 11 Mar 2014 15:08:09 -0700 (PDT)
In-Reply-To: <CAG4ve9+2bfaoZYSTKgfWNTQ=GtDZ+wQeioiqstVEK2yhp=Y=Tg@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>
Date: Tue, 11 Mar 2014 15:08:09 -0700
Message-ID: <CAC4O8c8ySdBMRRYVZY7MaDhSpGSwqwcUsjY4xdWMKPdTRL-NEA@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=KOI8-R
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id s2BM8C88019713
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 Tue, Mar 11, 2014 at 10:05 AM, Алексей Харьковский
<svetonomer AT gmail DOT com> wrote:

> Unfortunately I think it will not be completed yet.
> This path is extremely laborious and time-consuming.
> It will therefore be abandoned as a result.
> And each one will, as before, to use for its proven crutches that will
> wander around the various corners of the Internet.

Well I started out thinking its a bad idea but now I guess I'm convinced
integration sounds nice.

I think people should be ambitious and ask themselves what could be done to
get to the point where subcircuit designs could be gracefully distributed,
ideally with a default PCB layout/BOM that they map to.  People always say
you need different design rules, layouts etc. but truth is you often don't.
I'm sick of redesigning power supplies every project for example.

So you need either an ironclad convention for how (heavy) symbols used in
these modules are stored and versioned, or some way to freeze and integrate
them into a subdesign.  The first alternative is perfectly possible in
theory, but: a. it hasn't happened yet for gEDA, and b. more generally it
hasn't happened well for many other languages/libraries.  Also its not clear
that its better, assuming the conventions are honored enough to be useful,
the complexity is still there, its just enshrined as convention rather than
written down in the core code.

Britton