Remove *.egg-info directories in clean step
Removing the egg-info directory automatically in the 'clean' step means that if the build changes the egg-info, the change will not trip up the next build of the source package.
-
if the egg-info directory is generated by the build, then removing it is the right thing to do
-
if the egg-info directory is included in the upstream source, then deleting it causes no harm as dpkg-source warns on missing files in the source package but does not exit with error.
Merge request reports
Activity
pybuild-plugin-pyproject
only does out-of-tree builds, so the generateddist-info
metadata is in.pybuild/cpython3_*/build/*-*.dist-info
and will be cleaned up by the existing pybuildclean
actions.There are source packages including
dist-info
directories but I don't think they would get altered during the build ifpybuild-plugin-pyproject
is used. Do they get altered by the build if other build systems are used? Is there an example package where this is happening we should look at?
- Resolved by Stuart Prescott
added 5 commits
-
7ffdd65b...02ee81e4 - 3 commits from branch
python-team/tools:master
- 31eff8fd - Remove *.egg-info directories in clean step
- a5068b6d - Require initial . for .egg-info path match
-
7ffdd65b...02ee81e4 - 3 commits from branch