X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Injected-Via-Gmane: http://gmane.org/ To: geda-user AT delorie DOT com From: Kai-Martin Knaak Subject: Re: [geda-user] Pin mapping (separate symbols from mappings) Date: Tue, 20 Oct 2015 05:15:49 +0200 Lines: 25 Message-ID: References: <20151018204010 DOT 9cce6a231dcc296256e187bd AT gmail DOT com> <201510181843 DOT t9IIhmWo025346 AT envy DOT delorie DOT com> <20151018233004 DOT 78db1f9df1b1e68325c8639e AT gmail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8Bit X-Complaints-To: usenet AT ger DOT gmane DOT org X-Gmane-NNTP-Posting-Host: a89-182-62-119.net-htp.de User-Agent: KNode/4.14.1 Reply-To: geda-user AT delorie DOT com John Doty wrote: > On Oct 19, 2015, at 2:52 PM, Kai-Martin Knaak > wrote: > >> IMHO, the missing part in the puzzle is the notion of a "package" >> which delivers all information specific to a physical component. I >> deliberately did not write "contain" but "deliver". The package may >> include footprints viable for this component. Alternatively the >> package may refer to a footprint library by giving filenames of a >> footprints known to work. Which of the two is the most appropriate >> depends on circumstances. Therefore, the choice between inclusion >> or reference is up to the designer of the library of packages. > > But now you’re tangling upstream and downstream. How the footprint > library works depends on the layout tool. > A package provides a way to store all information related to a specific hardware component. It can be queried/read by any EDA tool. This includes applications for schematic capture, netlisters, layout tools, BOM creators, simulation tools, documentation assemblers, 3D modelers, and whatnot. So the terms "upstream" and "downstream" are meaningless with regard to the library of packages. ---<)kaimartin(>---