On Saturday 24 November 2007 18:38:00 Werner Hoch wrote:

> ------
> ; add a library with the command backend
> ; Syntax:
> ; (component-library-command "[listcommand]" "[getcommand]" "[name]")
> ;
> (component-library-command
>  "/home/werner/oss/geda/spicelib/scripts/gedaparts nxp_bipolar.index"
>  "/home/werner/oss/geda/spicelib/scripts/gedaparts nxp_bipolar.index"
>  "0_NXP bipolar transistors")
> (component-library-command
>  "/home/werner/oss/geda/spicelib/scripts/gedaparts nxp_diodes.index"
>  "/home/werner/oss/geda/spicelib/scripts/gedaparts nxp_diodes.index"
>  "0_NXP diodes")
> (component-library-command
>  "/home/werner/oss/geda/spicelib/scripts/gedaparts ti_opamps.index"
>  "/home/werner/oss/geda/spicelib/scripts/gedaparts ti_opamps.index"
>  "0_TI opamps")
> ------

"geda-clib.scm" gets clobbered everytime you upgrade gEDA.

Better would be to create a file "gedaparts.scm" with exactly the same 
contents in the same directory as geda-clib.scm.  Any file in this directory 
is assumed to be a Scheme file and is executed at startup.  (This 
functionality requires you to be running -unstable newer than 2007-10-21).

                                      Peter

-- 
Peter Brett

Electronic Systems Engineer
Integral Informatics Ltd

Attachment: signature.asc
Description: This is a digitally signed message part.


_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev

Reply via email to