A bunch of paths in MANIFEST.in were incorrect. We're also using both MANIFEST.in and package_data. I think we need one or the other, but not both. This moves all of the things in package_data to MANIFEST.in. We also want to be able to use the freshclam.yaml configuration file in enterprise. Moving the freshclam file inside of the anchore_engine module allows us the opportunity to potentially pull the freshclam file directly from the python package after it gets installed.
A bunch of paths in MANIFEST.in were incorrect. We're also using both MANIFEST.in and package_data. I think we need one or the other, but not both. This moves all of the things in package_data to MANIFEST.in. We also want to be able to use the freshclam.yaml configuration file in enterprise. Moving the freshclam file inside of the anchore_engine module allows us the opportunity to potentially pull the freshclam file directly from the python package after it gets installed.
Signed-off-by: Vijay Pillai vijay.pillai@anchore.com
What this PR does / why we need it:
Which issue this PR fixes (optional, in
fixes #<issue number>)(, fixes #<issue_number, ...)format, will close the issue when PR is merged: fixes #:Special notes: