X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
From: geda AT psjt DOT org (Stephan =?utf-8?Q?B=C3=B6ttcher?=)
To: Kai-Martin Knaak <kmk AT familieknaak DOT de>
Cc: geda-user AT delorie DOT com
Subject: Re: [geda-user] Who can you work with?
References: <CAM2RGhSma6sR9BJ=Y4nBejyVDizj5t4_efKLCR_yiDo7P+GiTQ AT mail DOT gmail DOT com>
	<nnidn5$kpk$1 AT blaine DOT gmane DOT org>
Date: Sat, 30 Jul 2016 18:41:30 +0200
In-Reply-To: <nnidn5$kpk$1@blaine.gmane.org> (Kai-Martin Knaak's message of
	"Sat, 30 Jul 2016 16:31:01 +0200")
Message-ID: <s6n1t2bm62t.fsf@blaulicht.dmz.brux>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
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

Kai-Martin Knaak <kmk AT familieknaak DOT de> writes:

> There is an informal don't-touch agreement in place when it comes to
> the default library of symbols. Consequently, the library has not seen
> significant changes since about 2006. This would be acceptable if the
> default lib were close to perfection. However, it is far from that. A
> flat, one stage hierarchy places exotics right next to standard parts.
> Digital components by DEC, anyone? This is aggravated by the fact that
> the symbols in the library are not ready-to use for the most common
> purpose (no footprint attribute).

PCB file have a very nice property: they are describing the geometry
of the layout without reference to anything external to the file.   I do
not particulary like the idea to change that with respect to fonts, as
discussed elsewhere.

Gschem files originally only carried references to library files for all
symbols.  A lot of existing files break if those libraries are changed.

Steps to resolve this may be

1. Allow deeper (unlimited) hierarchy of directories for symbols.

2. Move the existing library one level down, named legacy
   or something like that.

3. Put a rule into place that new symbols must not have the same names
   as one of the legacy ones.  Useful symbols can be copies/moved into
   the new hierarchy and need stay 100% compatible, in terms of pin
   positions and functional attributes.

4. Issue warings when opening designs referening legacy symbols, and
   provide hints how to embed or copy the symbols into the project's
   library for long term stability of the drawings.

5. Instrument gedasymbols to allow easy installation of contributed
   symbols into a well defined place in the library.  As suggested
   targets for this kind of download could be offered /usr/share/gEDA,
   ~/.local/share/gEDA, ./lib/, i.e., system, user, project.

-- 
Stephan