X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Date:	Wed, 19 Feb 2020 20:07:45 +0100 (CET)
From:	Roland Lutz <rlutz AT hedmen DOT org>
To:	"N (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject:	Re: [geda-user] Proposal: Library handling
In-Reply-To:	<20200219191719.91c12aa25f59646665633fe3@gmail.com>
Message-ID:	<alpine.DEB.2.20.2002191959350.9302@nimbus>
References:	<alpine DOT DEB DOT 2 DOT 20 DOT 2002181340190 DOT 1436 AT nimbus> <20200219191719 DOT 91c12aa25f59646665633fe3 AT gmail DOT com>
User-Agent:	Alpine 2.20 (DEB 67 2015-01-07)
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 Wed, 19 Feb 2020, N (nicklas DOT karlsson17 AT gmail DOT com) [via 
geda-user AT delorie DOT com] wrote:
> A little bit hard to distinguish between reference and embed

The difference is a semantic one.  "reference" means the symbol in the 
library is authoritative; "embed" means the symbol in the schematic is.

You could view "reference" as the way gEDA/gaf currently works, with the 
added perk that the symbol last seen in the library is included in the 
schematic.

With "reference", tools should update the schematic once they see a new 
symbol in the library (but probably ask the user for confirmation first). 
With "embed", tools should ignore any changes to the library symbol.

- Raw text -