MIME-Version: 1.0
In-Reply-To: <87ob83dodl.fsf@harrington.peter-b.co.uk>
References: <87ob83dodl DOT fsf AT harrington DOT peter-b DOT co DOT uk>
Date: Mon, 9 Sep 2013 11:31:29 +0400
Message-ID: <CAMvDHVDprzA9P2NBw-J0p=HRbs10-GkyOX+Ob+dMhseorf4QKg@mail.gmail.com>
Subject: Re: [geda-user] [RFC] Major changes to symbol/schematic libraries in geda-gaf
From: Vladimir Zhbanov <vzhbanov AT gmail DOT com>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
Precedence: bulk

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). So, co-ordinated
    directory naming in such a case would be appropriate.