X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.98.4 at av02.lsn.net
Message-ID: <559D4562.4020705@ecosensory.com>
Date: Wed, 08 Jul 2015 10:44:34 -0500
From: John Griessen <john AT ecosensory DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: [geda-user] libraries  (was:  . . . alive?)
References: <CAM2RGhQfPO31-1Uyc3kC7w286r0VD7c41UZEZcyYquzknCxbsQ AT mail DOT gmail DOT com> <20150707060409 DOT GB14357 AT localhost DOT localdomain> <CAOP4iL2C_LU=RQy5FWYF-7RrHW6tqhqqyFJGjkwLQ2AD7FiYJA AT mail DOT gmail DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1507071749560 DOT 6924 AT igor2priv> <CAM2RGhRA9Qt_PNUNzvaZ7OjjKDvrWobCJ2CptFYhBojtbxXXCA AT mail DOT gmail DOT com> <559C0F7D DOT 4020600 AT neurotica DOT com> <201507071805 DOT t67I5tFG012669 AT envy DOT delorie DOT com> <559C1B73 DOT 7040506 AT neurotica DOT com> <201507071838 DOT t67IcjWJ014955 AT envy DOT delorie DOT com> <20150707191750 DOT 918B98038A32 AT turkos DOT aspodata DOT se> <20150708074156 DOT GD13243 AT visitor2 DOT iram DOT es>
In-Reply-To: <20150708074156.GD13243@visitor2.iram.es>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: geda-user AT delorie DOT com

On 07/08/2015 02:41 AM, Gabriel Paubert (paubert AT iram DOT es) [via geda-user AT delorie DOT com] wrote:
> There are still subtle semantic details to discuss, but I see it
> basically as a front cache to the set of libraries (which may be defined
> by URLs as already suggested): if a symbol is in the cache you use it,
> otherwise you fetch the library item and copy it to the cache, where you
> can modify it to suit your need. You need an option in the GUI to update
> from the library (and resolve the case of several libraries defining
> the same symbol), but it has to be a deliberate act.

I like the idea of using a file based store for symbols/footprints even though it means
a library symbol gets copied needlessly and different versions with the same name can
happen.  It's important for it to be easy to verify your design is correct, and
isolating it from outside libraries that change form day to day by actions of others
is necessary for that.

A database might be used to enable searching through one's design as he adds to it,
and yet, it would load up its state from the project directory files, (or schematic embedded
paragraphs) so the source of the symbols is certain and easy to confirm.  A database
holding the design data chunks might even speed up creation of various kinds of netlists.
The way databases all have a "central control" attitude about them
is trouble for verifying correctness of designs though.