Do you mean vendor supplied footprint databases or BOM management? Footprint design doesn't account for much of my time and I don't remember the last time I had a footprint error, plus I have my own scripts for generating BGA footprints given parameters.
Same idea with BOM management, I have my own system for matching schematic part numbers to real part numbers. Schematics always specify generic part numbers, e.g. "0603 10V C0G 1nF", or for ICs "ADF4350" without suffixes, and every fab or prototype run is supplied with a "mappings" file that translates generics to detailed part numbers (very important because I substitute parts all the time); there is no way I want to be tied to a fixed part number specified on the schematic, and even vendor specific part numbers on the schematic are really just a placeholder for "an IC with these specs". The final BOM part numbers can and will differ from the schematic ones. This custom system is only possible because gEDA files are text files and are easy to parse. With vendor specific binary formats you are stuck with whatever system they provide. However, if you don't know any programming, then yes you are probably better off with a "ready out of the box" solution even if it isn't optimal...
OpenEMS has supported gEDA import for a while I think, the open source tools are certainly catching up...