X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=S2+EMKWtBvEw9ZXGBNAXRAuEaxT5yGIshtau9eJPkq0=;
	b=SY+rRLzKRcNBagjrws9cu4r9Rthmttiw4sbfgziUY6uOnVLKGbfoBZgJoYFKUxVYo7
	0q0nAXP/+mOBKsf1Kg4dZ9/lpexzB+C3uvnlo1uGY2h4tIOBpG+tN18FPeOy3stDEH52
	uDxcPWNP5uMSIQrwus2u6IeWp/JO3Nf/6bvZyU6ce18LrIicAAoeLXBIQf5+dyTRcoZS
	fMZfp2+FgBCnEyQiD3l5SO6F3FU6xrBScfsOMsALzNrNKT5bmXo8oBhxXnujX/84s3Tv
	vwTVpuYhpQZijRMu9tRxSd45MC7mdSQoTDOSubdL6YzmGJA42RPzPO68dnZky3Z13WWu
	OUaQ==
MIME-Version:	1.0
X-Received:	by 10.52.118.73 with SMTP id kk9mr14022836vdb.13.1378721405902;
	Mon, 09 Sep 2013 03:10:05 -0700 (PDT)
In-Reply-To:	<alpine.DEB.2.00.1309091104580.30022@igor2priv>
References:	<87ob83dodl DOT fsf AT harrington DOT peter-b DOT co DOT uk>
	<CAMvDHVDprzA9P2NBw-J0p=HRbs10-GkyOX+Ob+dMhseorf4QKg AT mail DOT gmail DOT com>
	<20130909083911 DOT GB22949 AT visitor2 DOT iram DOT es>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1309091104580 DOT 30022 AT igor2priv>
Date:	Mon, 9 Sep 2013 14:10:05 +0400
Message-ID:	<CAMvDHVCX-hnUP6gYa3wPQsCAqjWWt9zbyGEfN9xkDRmGxSpibg@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
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

2013/9/9, gedau AT igor2 DOT repo DOT hu <gedau AT igor2 DOT repo DOT hu>:
...
> On the other hand I do understand the opposite use case, when someone
> fixes a problem in his library and wants the fix to take effect on all
> schematics, immediately.
>
> I think making embedding symbols the default would be the best option
> here, with some optional mechanism to detect if the same symbol has a
> different version in the library. Coordinating a "push this library change
> to all my projects" this way would become explicit and probably could be
> controlled easier. This could be a separate script that the user could run
> after changing the library.

I don't agree here. Such a feature is already present in gschem.
Symbol versioning is aimed by the symversion= mechanism (see
http://wiki.geda-project.org/geda:master_attributes_list#symversion).
If you make some major changes in a library symbol, your projects
can be damaged by that if you do not carefully verify them, e.g.
if you change some pin positions. Minor changes (graphical,
hiding/showing some attributes and so on) are always OK.

- Raw text -