sometimes rebuilds (like macaron) contain additional py sources, like test files. Example: keras-1.12.1, the macaron rebuild contains:
- keras/src/activations/activations_test.py
- keras/src/applications/applications_test.py
- keras/src/applications/imagenet_utils_test.py
- keras/src/backend/common/backend_utils_test.py
This is acceptable assuming that macaron correctly fetches sources from github, just misses some inclusion filter the pypi build may have used.
The opposite is critical and should be flagged as non-equivalent (an additional file might have compromised the original build).
Note that this may change the original conceptual foundation of daleq as this would associate the two different wheels compared into two different roles "baseline package" and "verification package". A possible way is to add an additional argument for some algorithm to extract a list of sources from the repo, and then just use macaron (or the wheel it generates) as a way to do this.
sometimes rebuilds (like macaron) contain additional py sources, like test files. Example: keras-1.12.1, the macaron rebuild contains:
This is acceptable assuming that macaron correctly fetches sources from github, just misses some inclusion filter the pypi build may have used.
The opposite is critical and should be flagged as non-equivalent (an additional file might have compromised the original build).
Note that this may change the original conceptual foundation of daleq as this would associate the two different wheels compared into two different roles "baseline package" and "verification package". A possible way is to add an additional argument for some algorithm to extract a list of sources from the repo, and then just use macaron (or the wheel it generates) as a way to do this.