X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Mon, 9 Sep 2013 11:11:49 +0200 (CEST)
X-X-Sender:	igor2 AT igor2priv
To:	geda-user AT delorie DOT com
X-Debug:	to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From:	gedau AT igor2 DOT repo DOT hu
Subject:	Re: [geda-user] [RFC] Major changes to symbol/schematic libraries
	in geda-gaf
In-Reply-To:	<20130909083911.GB22949@visitor2.iram.es>
Message-ID:	<alpine.DEB.2.00.1309091104580.30022@igor2priv>
References:	<87ob83dodl DOT fsf AT harrington DOT peter-b DOT co DOT uk> <CAMvDHVDprzA9P2NBw-J0p=HRbs10-GkyOX+Ob+dMhseorf4QKg AT mail DOT gmail DOT com> <20130909083911 DOT GB22949 AT visitor2 DOT iram DOT es>
User-Agent:	Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version:	1.0
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

On Mon, 9 Sep 2013, Gabriel Paubert wrote:

> On Mon, Sep 09, 2013 at 11:31:29AM +0400, Vladimir Zhbanov wrote:
>> 1.  I'd prefer to use shorter default directory names without
>>     special characters such as dash, e.g. just 'geda' or 'gaf', in
>>     order to facilitate scripting.
>>
>> 2.  Honestly, I don't understand why a project directory should
>>     screen the user or system directory with the same name. I'd
>>     prefer to see them mixed in gschem with project directory
>>     symbols hiding user or system ones having the same names.
>>     To distinguish project, user and system symbols, they could be
>>     graphically separated, say, having icons with different
>>     colors. I like the workflow when I have locally modified
>>     versions of my user library symbols in a project directory.
>
>>     I'd even prefer to somehow force gschem make local copies of
>>     new symbols every time I add them in a schematic, and further
>>     work with these copies (it also would make any project
>>     independent of any library changes).
>
> That would be my preferred way too. In this case, the whole project
> becomes completely independent of what is in the libraries when
> you update the system. Or when you switch machines (which I do
> all the time with 3 different workplaces).
>
> Self-contained projects are really a good thing, at least when
> I used OrCad, there was a command "Archive parts in schematics"
> which took all the parts used in the schematics and put them
> in a single library file. That was a very nice feature, actually
> the one I mostly miss.
>

I agree. I run into this problem from time to time that the schematics I 
wanted to use on another computer or share depends on a symbol in a 
library that I forgot to commit or fetch.

On the other hand I do understand the opposite use case, when someone 
fixes a problem in his library and wants the fix to take effect on all 
schematics, immediately.

I think making embedding symbols the default would be the best option 
here, with some optional mechanism to detect if the same symbol has a 
different version in the library. Coordinating a "push this library change 
to all my projects" this way would become explicit and probably could be 
controlled easier. This could be a separate script that the user could run 
after changing the library.

Regards,

Tibor

- Raw text -