X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f Date: Mon, 9 Sep 2013 01:53:22 -0400 Message-Id: <201309090553.r895rMxU021173@envy.delorie.com> From: DJ Delorie To: geda-user AT delorie DOT com In-reply-to: <87mwnmblx2.fsf@harrington.peter-b.co.uk> (message from Peter TB Brett on Mon, 09 Sep 2013 06:31:53 +0100) Subject: Re: [geda-user] [RFC] Major changes to symbol/schematic libraries in geda-gaf References: <87ob83dodl DOT fsf AT harrington DOT peter-b DOT co DOT uk> <201309082106 DOT r88L6uGB008410 AT envy DOT delorie DOT com> <87ppsjas54 DOT fsf AT harrington DOT peter-b DOT co DOT uk> <201309082208 DOT r88M8atf023306 AT envy DOT delorie DOT com> <87mwnmblx2 DOT fsf AT harrington DOT peter-b DOT co DOT uk> 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 > Okay --- so you want there to be an API method to request a resource > X that's located in the same library as another resource Y. Yeah, something like that. The pcb netlister would have to pass that library info to pcb so it knows which footprint library to pull from, of course, as will other netlisters if their files are bundled. So if the pcb netlister sees a footprint= in a symbol from library A, it needs to know "from library A" so it can act accordingly. > It's probably something we could support in the future I think this will be more relevent if I ever get around to doing the component database idea I've mentioned before, in which case the database is generally *not* a file somewhere.