Refactor current source writing logic
Summary
This issue is to raise the point that currently all parsed source config from the fd.o json files, is written to the bst files. This is not correct as there are many examples of config options set in fd.o, that is not supported by buildstream.
Steps to reproduce
Run the current parse tools and inspect the produced .bst files.
Example Project
N/A
What is the current issue behavior?
Currently if the parse tool is run, you will see in the .bst files many 'source' options, which have invalid options associated with them.
What is the expected correct behavior?
The file writer should have a generic way to allow for custom logic to be implemented regarding each source type, so any unsupported commands can be modified or removed, before the file gets written.
Relevant logs and/or screenshots
N/A
Possible fixes
The logic which needs fixing is located in elements/autotool.py