Hi Blood_Hawk23,
if I may offer a suggestion, which comes from years of painstakingly modding and archiving away to preserve the work done, if I were you I'd do a separate *.bgl for each weapon you built.
Although it seems a lot of work, a single
[weapon_name].bgl would help a lot identifying what's inside one's weapons CFS2 root database at first glance.
This, in turn, will make real easy:
- installing
- un-installing
- creating dedicated installs
- rebuilding the sim to one's previous customisation after a crash
- finding a specific missing weapon which is causing CFS2 error messages and/or mission CTD
- classifying and archiving the download
- eventually debugging a faulty *.bgl causing either troubles or CTD's
A single, generic
weapons.bgl library would not help pinpoint one or all of the above needs, especially for computer everyday users that do not need professional skills to operate sufficiently a pc. I mean all of those people who could find difficult having to use a *.bgl analysing utility.
If you feel the above would be a lot of work, you could at least group together similar weapons, like a single *.bgl comprising all of GP bombs whose only difference would be the different weight from one another. Of course, group them by nationality according to CFS2 stock standards.
Thank you for your work! 
Cheers!
KH