X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Mon, 19 Oct 2015 17:06:25 -0400
Message-Id: <201510192106.t9JL6PAx006922@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <n03l6g$91u$1@ger.gmane.org> (message from Kai-Martin Knaak on
	Mon, 19 Oct 2015 22:52:32 +0200)
Subject: Re: [geda-user] Pin mapping (separate symbols from mappings)
References: <20151018204010 DOT 9cce6a231dcc296256e187bd AT gmail DOT com> <201510181843 DOT t9IIhmWo025346 AT envy DOT delorie DOT com> <20151018233004 DOT 78db1f9df1b1e68325c8639e AT gmail DOT com> <n03l6g$91u$1 AT ger DOT gmane DOT org>
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


> By default, the schematic references the package and stores the picks of 
> the author.

My idea allows for "something" to choose the package based on whatever
else the user might have provided.  For example, if I specify SOT-23
and my library only has one SOT-23 option, that's enough to specify
the package without having to explicitly specify the package.

That way you can reduce the set of matching parts a little at a time
instead of having to pick a final package up front.

> This sounds a lot like the "package" scenario I described above.

Yup :-)

My way of using it would be to have symbols keep their symbolic pin
"numbers" like A,B,Y or B,C,E.  Footprints would have numeric pin
numbers as usual.  The "package" would include a mapping from symbolic
to numeric pins for that package.  The netlister would apply the
conversion based on which "package" was chosen.

> Except that I deliberately did not imagine a (relational) data base
> but plain files.

Me neither, and since you're quoting what was originally written by
me, let me add this quote from later on in that document:

"How is the database stored? I'm not going to specify that - it's
irrelevent."