This request is to enhance genattrib.py and about.py to accept an archive of AboutCode files as an alternative input instead of pointing to a directory.
The use case is to make it easier for a development team (who does not embed AboutCode files inside their codebase) to keep a "portable" set of AboutCode files to use in Attribution generation, as well as make it easier to automate the various AboutCode steps.
The enhancement would be an option for genattrib.py and about.py to accept an archive of AboutCode files as input_path, extract that archive locally in the AboutCode installation and use that data for Attribution (or inventory generation) with the assumption that the Resource path in the component_list parameter will be relative to the archive file.
We should only need to support relatively simple single-level archive formats such as .tar. .zip, .7z or .xz because there is no logical requirement for multi-stage compression here.
This request is to enhance genattrib.py and about.py to accept an archive of AboutCode files as an alternative input instead of pointing to a directory.
The use case is to make it easier for a development team (who does not embed AboutCode files inside their codebase) to keep a "portable" set of AboutCode files to use in Attribution generation, as well as make it easier to automate the various AboutCode steps.
The enhancement would be an option for genattrib.py and about.py to accept an archive of AboutCode files as input_path, extract that archive locally in the AboutCode installation and use that data for Attribution (or inventory generation) with the assumption that the Resource path in the component_list parameter will be relative to the archive file.
We should only need to support relatively simple single-level archive formats such as .tar. .zip, .7z or .xz because there is no logical requirement for multi-stage compression here.