X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Mon, 10 Mar 2014 19:28:08 +0100 (CET) From: Roland Lutz To: geda-user AT delorie DOT com Subject: Re: [geda-user] identical symbol names In-Reply-To: <20140310161148.5BB628020170@turkos.aspodata.se> Message-ID: References: <20140127234944 DOT 924148045B78 AT turkos DOT aspodata DOT se> <20140128201110 DOT DF7D78045B78 AT turkos DOT aspodata DOT se> <20140129072550 DOT GA24560 AT localhost DOT localdomain> <86CABBE6-EE80-4347-B7AA-3F5A8DA4C658 AT noqsi 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> <20140310161148 DOT 5BB628020170 AT turkos DOT aspodata DOT se> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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 IMHO, these are two separate problems: 1. multiple symbols with the same basename but different paths, and 2. having self-contained schematic files. 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.