X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Wed, 12 Mar 2014 15:00:53 +0100 (CET)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] identical symbol names
In-Reply-To: <20140311110310.A24798020170@turkos.aspodata.se>
Message-ID: <alpine.DEB.2.10.1403121445360.27761@home.local>
References: <CAG4ve9LgHNoVZoGaGgF67tadJ_n=L6Uy1g=UPPrkM0fL6Rgufw AT mail DOT gmail DOT com> <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> <86CABBE6-EE80-4347-B7AA-3F5A8DA4C658 AT noqsi DOT com>
 <CAG4ve9LX0mYk2a1zpfWJJC=OP5Weq9pt3PF7_Nqx5vX4wpR=Bg AT mail DOT gmail DOT com> <1394402434 DOT 2151 DOT 28 DOT camel AT AMD64X2 DOT fritz DOT box> <20140309235005 DOT 783608020170 AT turkos DOT aspodata DOT se> <531D222C DOT 8060101 AT ecosensory DOT com> <20140310103056 DOT E1B1D8020170 AT turkos DOT aspodata DOT se>
 <CAGRhJMajnGHi8WembiDtBPV9V8E0hXOUgaDoWXHyQ-BMXNiMYg AT mail DOT gmail DOT com> <20140310161148 DOT 5BB628020170 AT turkos DOT aspodata DOT se> <alpine DOT DEB DOT 2 DOT 10 DOT 1403101921380 DOT 13502 AT home DOT local> <20140311110310 DOT A24798020170 AT turkos DOT aspodata DOT se>
User-Agent: Alpine 2.10 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="8323329-1658560993-1394632853=:27761"
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

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323329-1658560993-1394632853=:27761
Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Tue, 11 Mar 2014, karl AT aspodata DOT se wrote:
>> 2. having self-contained schematic files.
>
> What's the use case for that, is it only for distributing schematics,
> archiving, make your disk tree look nicer or is it for something else
> also ?

It's a matter of preference and habit.  Some people seem to prefer 
minimizing the risk of inadvertently editing multiple copies of a file 
while others prefer minimizing the risk of a symbol dependency suddenly 
being different or lost or just not there when needed.

With “non-authoritative embedding”, you will have a copy of the symbol 
when you need it, won't miss a (potentially incompatible) change in the 
library but still have a single place where things are stored.


>> Maybe the second problem could be solved by "embedding" each symbol the
>> first time it is referenced while marking the embedded symbol as
>> non-authoritative.  This way, the tools could use the included symbol in
>> case the library symbol is not found, and otherwise compare the symbol to
>> the library version and, if outdated, offer to update it.

--8323329-1658560993-1394632853=:27761--