X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f X-Recipient: geda-help AT delorie DOT com From: John Doty Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: multipart/alternative; boundary=Apple-Mail-1-430467473 Subject: Re: [geda-help] Adding new gschem symbols? Date: Sun, 14 Oct 2012 16:05:38 -0600 In-Reply-To: To: geda-help AT delorie DOT com References: <1349966191 DOT 2412 DOT 33 DOT camel AT AMD64X2 DOT fritz DOT box> <20121012100446 DOT 93D648096B1E AT turkos DOT aspodata DOT se> <20121013174902 DOT 160C98117B42 AT turkos DOT aspodata DOT se> Message-Id: X-Mailer: Apple Mail (2.1085) Reply-To: geda-help AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-help AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --Apple-Mail-1-430467473 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On Oct 14, 2012, at 2:27 PM, Benjamin Bergman wrote: >=20 > On Oct 13, 2012 12:50 PM, "Karl Hammar" wrote: > > Well you could possible use the md5sum of the sym file, what about: > > > > $ md5sum git/openhw/share/gschem/diode.sym > > cc2da042b5ea5afd65f4153bfff79b92 git/openhw/share/gschem/diode.sym > > > > And in the .sch file, this file is referenced by: > > > > C 18600 19900 1 0 0 diode.sym md5=3Dcc2da042b5ea5afd65f4153bfff79b92 >=20 > I think this is the way to go. This is essentially how all content is = tracked and referenced in git and adds a layer of corruption detection, = while costing very little in terms of resources or infrastructure. Shudder. That assumes that symbols rarely change. But a sensible way to = use gEDA is to have project-local symbols that change as packaging or = other part selection attributes change. John Doty Noqsi Aerospace, Ltd. http://www.noqsi.com/ jpd AT noqsi DOT com --Apple-Mail-1-430467473 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii


On Oct 13, 2012 12:50 PM, "Karl Hammar" <karl AT aspodata DOT se> wrote:
> Well you could possible use the md5sum of the sym file, what = about:
>
> $ md5sum git/openhw/share/gschem/diode.sym
> cc2da042b5ea5afd65f4153bfff79b92 =  git/openhw/share/gschem/diode.sym
>
> And in the .sch file, this file is referenced by:
>
> C 18600 19900 1 0 0 diode.sym = md5=3Dcc2da042b5ea5afd65f4153bfff79b92

I think this is = the way to go. This is essentially how all content is tracked and = referenced in git and adds a layer of corruption detection, while = costing very little in terms of resources or infrastructure.

Shudder. That assumes that symbols rarely change. But = a sensible way to use gEDA is to have project-local symbols that change = as packaging or other part selection attributes change.

John Doty              Noqsi = Aerospace, Ltd.

http://www.noqsi.com/

jpd AT noqsi DOT com

= --Apple-Mail-1-430467473--