X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Tue, 8 Sep 2015 14:53:10 -0400
Message-Id: <201509081853.t88IrAak001304@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <11875D68-7D82-48AB-8850-C5C3BCCF64EC@noqsi.com> (message from
	John Doty on Tue, 8 Sep 2015 10:47:12 -0600)
Subject: Re: [geda-user] Desired changes (was:"New experimental netlist features")
References: <alpine DOT DEB DOT 2 DOT 11 DOT 1509031356150 DOT 13201 AT nimbus> <55E8773B DOT 9000902 AT jump-ing DOT de> <alpine DOT DEB DOT 2 DOT 11 DOT 1509031846370 DOT 7163 AT nimbus> <55E8831A DOT 8050307 AT jump-ing DOT de> <alpine DOT DEB DOT 2 DOT 11 DOT 1509032004020 DOT 10628 AT nimbus> <55E891FA DOT 2010509 AT jump-ing DOT de> <alpine DOT DEB DOT 2 DOT 11 DOT 1509032039300 DOT 14871 AT nimbus> <BC7E3E69-4914-4654-B020-1338C71E0CDB AT noqsi DOT com> <201509032030 DOT t83KU1Yq017045 AT envy DOT delorie DOT com> <55E97A3E DOT 2070402 AT jump-ing DOT de> <69B8B3F4-A6E4-43E9-9055-C63A5D6A3707 AT noqsi DOT com> <msfjma$340$1 AT ger DOT gmane DOT org> <alpine DOT DEB DOT 2 DOT 00 DOT 1509060518220 DOT 6924 AT igor2priv> <msidqe$66h$1 AT ger DOT gmane DOT org> <D2219618-B906-432B-B11A-C108DA9FCBF9 AT noqsi DOT com> <CAOP4iL3JkWC4Nuw8vDOBDR4Zk4OD2xwrMwHXp-ZihPom5Wmfwg AT mail DOT gmail DOT com> <43CA04C5-47B7-4DA4-8005-3A2D4E9D0E47 AT noqsi DOT com> <20150908162514 DOT 43142577ec15e48c50950a18 AT gmail DOT com> <CD93E147-F22E-4CA2-9793-FAAA5558486D AT noqsi DOT com> <20150908182504 DOT 196a11571c68bc63ef8e4c27 AT gmail DOT com> <11875D68-7D82-48AB-8850-C5C3BCCF64EC AT noqsi DOT com>
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


> > For me it seems like a problem to never be allowed to change an old symbol without breaking schematics using them.
> 
> Or to be able to remove old rusting symbols from the distributed library.

Perhaps we're finally seeing the dark side of a toolkit approach - the
toolkit leaves too much of the management to the user?

> And then, ngspice users want an ngspice-oriented library, pcb users
> want a pcb-oriented library, VHDL users want a VHDL-oriented
> library, etc. It seems to me that a project library management tool
> would be very useful.

Yet another task that would fit into a proposed component database
manager?  Or is this something that the other tools need to know
about?