summaryrefslogtreecommitdiff
path: root/requirements
diff options
context:
space:
mode:
authorChandan Singh <csingh43@bloomberg.net>2019-02-18 18:11:31 +0530
committerChandan Singh <csingh43@bloomberg.net>2019-02-18 18:11:31 +0530
commite0f0a01d678aecfeb57372721e9d78a148487f48 (patch)
treea03d16cb1c277853f19b4843c0a3518c28f49c49 /requirements
parentef85e3b295bdec7ad8c0b34e16c56034073d5031 (diff)
downloadbuildstream-e0f0a01d678aecfeb57372721e9d78a148487f48.tar.gz
requirements/Makefile: exclude pkg-resources
Having `pkg-resources` in requirements files is never the right thing as it is not really a package that one can install. This is basically an artifact of Debian-based systems providing incorrect metadata to pip. See [this pip issue](https://github.com/pypa/pip/issues/4022) and [this Ubuntu issue](https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1635463) for more background.
Diffstat (limited to 'requirements')
-rw-r--r--requirements/Makefile2
1 files changed, 1 insertions, 1 deletions
diff --git a/requirements/Makefile b/requirements/Makefile
index c49a2e2d0..0f4d885fa 100644
--- a/requirements/Makefile
+++ b/requirements/Makefile
@@ -17,5 +17,5 @@ all: $(REQUIREMENTS_TXT)
$(eval VENVDIR := $(shell mktemp -d $(CURDIR)/.bst-venv.XXXXXX))
$(VENV) $(VENVDIR)
$(VENV_PIP) install -r $^
- $(VENV_PIP) freeze -r $^ > $@
+ $(VENV_PIP) freeze -r $^ | grep -v pkg-resources > $@
rm -rf $(VENVDIR)