software-discovery-tool
software-discovery-tool copied to clipboard
openmainframeproject
Software Discovery Tool
Resolved issue #184 The PR modifies the script to standardize the behavior by allowing generation of all available ibm-validated distribution sources without requiring additional arguments, simplifying usage and aligning it...
Fixed issue #110 which was addressed in the [PR](https://github.com/openmainframeproject/software-discovery-tool/pull/124). I have addressed the changes which were requested on the PR
While generating the sources for Fedora, I got a build timeout while it was building Fedora 40. Full traceback below (the 404 errors are unrelated and a known issue). Essentially,...
Hi @pleia2 @arshPratap, as discussed earlier in the issue #120, this is the current implementation of the react front-end which I worked upon during my LFX mentorship. I've also attached...
Usually, the script a single argument to create data files, for instance: ./package_build.py debian In the case of Debian, this will generate all the supported versions: Saved! filename: Debian_Bullseye_List.json Saved!...
As working on IBM-Validated-Software List I noticed that after some time some packages in a file get expired or modified. That's the case for every file that we've in our...
Fixes to add packages compatible with z/OS in response to issue #110. @arshPratap @pleia2 please take a look.
There are various linting standards in python. Most commonly used are: * `PEP8` * `Flake8` * `Pylint` We need to discuss on which linting format do we want to use.
As listed in the contribution guidelines [Link](https://github.com/openmainframeproject/software-discovery-tool/blob/master/docs/Contribute.md): 1. The branch name should be of the format Software-Discovery-Tool-feature_name. 2. The commits should include a DCO signoff A github action should be...
