X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-UW-Orig-Sender:	fpm AT homer01 DOT u DOT washington DOT edu
Date:	Wed, 13 Jan 2016 08:47:00 -0800 (PST)
From:	"Frank Miles (fpm AT u DOT washington DOT edu) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	"Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject:	Re: [geda-user] Re: off-board parts/wiring
In-Reply-To:	<CAJXU7q9OTdMpLMr6GbnCqLv_bHxjzOUsKgt-ovFdh5Qri9VUfQ@mail.gmail.com>
Message-ID:	<alpine.LRH.2.01.1601130844310.4756@homer01.u.washington.edu>
References:	<CAM2RGhS4L-ch6FEcLtdSt0vA0BdQZvq+AuFDP+9ea7Ftd=AALg AT mail DOT gmail DOT com> <8444F816-17CE-4A56-A982-4A60DEDA72B8 AT noqsi DOT com> <alpine DOT LRH DOT 2 DOT 01 DOT 1601040930510 DOT 18447 AT homer02 DOT u DOT washington DOT edu> <AF9F11C6-29A4-4558-85C8-973AB80BADFF AT noqsi DOT com>
	<CAC4O8c_ckyybeLDoV9oGM8cdH08goyqw6zG0eFn4dYdG_wchwg AT mail DOT gmail DOT com> <alpine DOT LRH DOT 2 DOT 01 DOT 1601060831110 DOT 31979 AT homer02 DOT u DOT washington DOT edu> <29B50AD8-DCD0-4048-B888-711C5D8E1E65 AT noqsi DOT com> <alpine DOT LRH DOT 2 DOT 01 DOT 1601070826250 DOT 1447 AT homer01 DOT u DOT washington DOT edu>
	<20160107175042 DOT 5e06aad2bf09818a8886d6f7 AT gmail DOT com> <alpine DOT LRH DOT 2 DOT 01 DOT 1601080823510 DOT 14656 AT homer03 DOT u DOT washington DOT edu> <20160108182822 DOT 3c4b5f2d183143b4a41680dd AT gmail DOT com> <alpine DOT LRH DOT 2 DOT 01 DOT 1601111041200 DOT 28725 AT homer02 DOT u DOT washington DOT edu> <201601111903 DOT u0BJ3A9a005050 AT envy DOT delorie DOT com>
	<5693FF30 DOT 1020208 AT iee DOT org> <alpine DOT LRH DOT 2 DOT 01 DOT 1601120839240 DOT 16881 AT homer01 DOT u DOT washington DOT edu> <CAJXU7q9OTdMpLMr6GbnCqLv_bHxjzOUsKgt-ovFdh5Qri9VUfQ AT mail DOT gmail DOT com>
User-Agent:	Alpine 2.01 (LRH 1217 2009-02-23)
MIME-Version:	1.0
X-PMX-Version:	6.2.1.2493963, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.1.13.163616
X-PMX-Server:	mxout22.s.uw.edu
X-Uwash-Spam:	Gauge=X, Probability=10%, Report='
	TO_IN_SUBJECT 0.5, HTML_00_01 0.05, HTML_00_10 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, DATE_TZ_NA 0, NO_URI_HTTPS 0, REFERENCES 0, __ANY_URI 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CT_TEXT_PLAIN 0, __FORWARDED_MSG 0, __FRAUD_BODY_WEBMAIL 0, __FRAUD_WEBMAIL 0, __HAS_FROM 0, __HAS_MSGID 0, __IN_REP_TO 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __REFERENCES 0, __SANE_MSGID 0, __SUBJ_ALPHA_NEGATE 0, __TO_IN_SUBJECT 0, __TO_MALFORMED_2 0, __URI_NO_PATH 0, __URI_NO_WWW 0, __URI_NS , __USER_AGENT 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 Tue, 12 Jan 2016, Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com] wrote:

> 
> 
> On 12 Jan 2016 17:02, "Frank Miles (fpm AT u DOT washington DOT edu) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote:
> >
> 
> > Perhaps I'm confused.  I thought I had read that the netlist import was
> > deprecated, and that the proper way of importing the netlist was through
> > PCB:File/Import Schematics.  If netlist import is still equally valid,
> > then please accept my apology for the needless noise.
> >
> >         -F
> 
> The import mechanism was added as a more integrated way of retrieving this information, rather than relying on an external tool, 
> gsch2pcb to process your existing design file and make edits. (This tool had to read and make edits to the board files, so
> represented a barrier to format changes. This was probably not the initial motivation of the new mechanism, but represents a big
> plus point to its existence).
> 
> Underlying the mechanism is a netlist backend for gnetlist which describes the components and nets of the design using a series of
> pcb action commands. These are executed by pcb on the open design, and in turn update the internal view of the netlist.
> 
> The "old" netlist format is not deprecated, although it does not convey all of the information about parts etc.. (gsch2pcb managed
> that aspect based upon a template file a separate gnetlist backend would populate with all the parts of a given design).
> 
> Since gsch2pcb and associated netlist backends were in a separate code base to pcb, this represented a compatibility problem if ever
> we changed things with the file format. The new backend lives with PCB (iirc), so merely relies on gnetlist keeping a stable scheme
> api and command line interface.
> 
> You might be interested to know that the update mechanism can be wired to call a makefile (or other scripts?) to generate the
> required data, so it is infact quite general. Only the "schematics" attributes are really assumed to come from a simple gschem work
> flow.
> 
> At some point, I may update xgsch2pcb to use this new mechanism, rather than gsch2pcb. It seems redundant to update gsch2pcb itself
> though.
> 
> Peter

Thanks to you - Peter, Nicklas, and DJ - for the explanations.
One more question - where can I read about the differences, and
how this update mechanism might be used?

 	-F

- Raw text -