Comment 2 for bug 1839705

Hi Jeff,
If you want to know why the .dcm files exist, the reason is due to the fact the early time Eeschema was using in the school (a very long time ago...) most of computers was using a slow link for the network connection.
I mean IDE network cards with a rate of 2400 bits per seconds.
So, Loading a few library files from the server (a local installation was not an acceptable solution) was a matter of minutes.
(Note also a similar file was existing for .mod footprint files, but was removed some time ago)

Therefore I added a small file associated to library files to load the list of symbols, their keywords and doc links) to be able to load the symbol list with an acceptable delay.

Note also these time constraints are existing now (see the fp-info-cache file).
But nowadays the .dcm file constraint is no longer existing, and this file is not needed, as long as the symbols are living in one file by library, and not in a lot of separate files.