X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Thu, 22 Mar 2018 15:06:12 +0100 (CET)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] current gnetlist from git and hierarchy
In-Reply-To: <20180321220800.6EB79807DEBE@turkos.aspodata.se>
Message-ID: <alpine.DEB.2.20.1803221457170.1629@nimbus>
References: <20180312013908 DOT 3dbbb5bc AT swips DOT iqo DOT uni-hannover DOT de> <alpine DOT DEB DOT 2 DOT 20 DOT 1803202117510 DOT 2530 AT nimbus> <20180321152652 DOT CDB05807DEBE AT turkos DOT aspodata DOT se> <alpine DOT DEB DOT 2 DOT 20 DOT 1803212112330 DOT 1501 AT nimbus> <20180321220800 DOT 6EB79807DEBE AT turkos DOT aspodata DOT se>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
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

On Wed, 21 Mar 2018, karl AT aspodata DOT se wrote:
> You must be thinking about some other tree.

I thought you were referring to PREFIX/share/gEDA/sym/, sorry.  But the 
essence is the same: the gedasymbols.org CVS repository can't be included 
recursively because, in the case of a name conflict, it would be unclear 
whose symbols to use.  This has always been the case; the new error check 
just makes it obvious that there's a potential source of silent errors.

The solution is to just include those symbol directories which you are 
using, and resolving potential name conflicts between them by hand.