X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Mon, 11 Jan 2016 14:03:10 -0500 Message-Id: <201601111903.u0BJ3A9a005050@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: (geda-user AT delorie DOT com) Subject: Re: [geda-user] Re: off-board parts/wiring References: <8444F816-17CE-4A56-A982-4A60DEDA72B8 AT noqsi DOT com> <29B50AD8-DCD0-4048-B888-711C5D8E1E65 AT noqsi DOT com> <20160107175042 DOT 5e06aad2bf09818a8886d6f7 AT gmail DOT com> <20160108182822 DOT 3c4b5f2d183143b4a41680dd AT gmail 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 > To repeat my previous question: what's so hard about getting pcb to > understand a circuit from a netlist? This would allow a variety of > custom "schematic alterations" that cannot happen if gPCB reads the > schematic directly. Since pcb *does* read netlists as part of its normal import, I guess the answer is "it's not hard". It imports other information too, though, like footprint selections. It sounds like your problem isn't getting pcb to understand a netlist, it's getting the tools to emit the right netlist.