Mail Archives: geda-user/2015/09/08/14:16:41
On Sep 8, 2015, at 11:33 AM, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>>>>>>> The basic problem is that referencing symbols in a global library requires that the global library not change. So, if you change the default library, you break old projects.
>>>>>
>>>>> Not if symbols are copied into library and only updated then pressing the update button.
>>>>>
>>>>
>>>> Not true. Symbols are, by default, accessed by referring to the symbol file name in gschem and gnetlist. Simply relaunching gschem or running gnetlist effectively updates your symbols from whatever the symbol files contain. You can embed symbols in the schematics, and that’s a solution in some cases, but it is too inflexible for others.
>>>>
>>>
>>> For me it seems like a problem to never be allowed to change an old symbol without breaking schematics using them.
>>>
>>
>> Or to be able to remove old rusting symbols from the distributed library. And then, ngspice users want an ngspice-oriented library, pcb users want a pcb-oriented library, VHDL users want a VHDL-oriented library, etc. It seems to me that a project library management tool would be very useful.
>
> Yes it is rather common with a few project specific components or similar.
>
I often have many project-specific components. A project may have a default opamp, a default bypass cap, a default resistor package, etc. So, I have some moderately heavy symbols.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
- Raw text -