We have a collection of federated repositories which share a reference to a canonical set of third-party dependencies. There is a single requirements.txt which is imported by every repository, and not every repository uses all the entries in that requirements file.
I'm discovering that the pip_import rules install everything in the requirements file, regardless of whether it is needed in the dependencies of the target currently begin built. This is suboptimal, particularly since some packages may have errors which prevent them from being built on the given system.
Instead, we should only install the package set required to satisfy the required build targets.
We have a collection of federated repositories which share a reference to a canonical set of third-party dependencies. There is a single
requirements.txtwhich is imported by every repository, and not every repository uses all the entries in that requirements file.I'm discovering that the
pip_importrules install everything in the requirements file, regardless of whether it is needed in the dependencies of the target currently begin built. This is suboptimal, particularly since some packages may have errors which prevent them from being built on the given system.Instead, we should only install the package set required to satisfy the required build targets.