AD18 and Git

[julianhigginson]

you should be able to have lots of schlib and pcblib files in an integrated library project?
not 100% certain but it'd be fast to try.

I use a dblib now. so I just have a single DBlib file, with the separate library files in a folder structure "below" that, and the dblib file points to a database (previously excel file, now migrating to SQL) which has a record for each part, that links to the schlib and pcblib files each part in the database needs, in reference to their location from the dblib file.

[Gibson486]

the only sane way to work around having independent user operated part libraries in a version control system is to have part libraries that only contain one part each.

YES it's a bit of a pain, but it means in a morning you can create library parts for a new ADC, someone else can create library parts for a new processor and an I2C eeprom, and someone else can correct pin numbering errors they discovered on a LED footprint, and the results can easily and simply get merged as people just commit their work.

I am exactly in the middle of this. Making an "internal library" and I am not yet sure, how it is best solved. This library is to be used by a small university group, and it is important people can easily add and change footprints, while keeping track of changes.
My initial thought was to have ALL components as a integrated library, one library for each component.
But that would mean you have to "install" say 1000 integrated libraries in Altium, seems insane to me. Or am I missing out on something here?

Each library can contain multiple parts. So, in your resistor library, you have a specific 10K resistor as a single part, which is probably designated by a vendor part number. You do not really turn it into an integrated library until your are sure it will not change. In my environment, I do not even bother with the integrated library. The thing is, if you work in a heavily regulated industry, the steps will seem absurd, but they will be required by your internal regulatory group.  If that means you will have thousands of integrated libraries in your platform, then that is what it means.

[JacobEFOvergaard]

the only sane way to work around having independent user operated part libraries in a version control system is to have part libraries that only contain one part each.

YES it's a bit of a pain, but it means in a morning you can create library parts for a new ADC, someone else can create library parts for a new processor and an I2C eeprom, and someone else can correct pin numbering errors they discovered on a LED footprint, and the results can easily and simply get merged as people just commit their work.

I am exactly in the middle of this. Making an "internal library" and I am not yet sure, how it is best solved. This library is to be used by a small university group, and it is important people can easily add and change footprints, while keeping track of changes.
My initial thought was to have ALL components as a integrated library, one library for each component.
But that would mean you have to "install" say 1000 integrated libraries in Altium, seems insane to me. Or am I missing out on something here?

Each library can contain multiple parts. So, in your resistor library, you have a specific 10K resistor as a single part, which is probably designated by a vendor part number. You do not really turn it into an integrated library until your are sure it will not change. In my environment, I do not even bother with the integrated library. The thing is, if you work in a heavily regulated industry, the steps will seem absurd, but they will be required by your internal regulatory group.  If that means you will have thousands of integrated libraries in your platform, then that is what it means.

Ah then I simply misunderstood the point. I thought every single component should be ONE integrated library itself. Right now I am also making it with an integrated library for say resistors. However the thing I find hard to deal with here is, if two people change something in the same integrated library. We will not be able to easily see which part of the integrated library was changed.

Initially we are handling the library on GitHub, at least until we can try out the Altium Vault.