Comment 14 for bug 1816644

Thomas, if I understand comment #13 it's basically what I did for tricircle [1]; separating those dependencies we want from git into their own requirements file?

Based on [1] this does work, but it kind of goes against the purpose of a requirements.txt file that can be used to install all the reqs for a repo/project since in this case anything installing the project needs to know to install using both the requirements.txt and os-required-projects.txt.. Just my $0.02 and based on my (limited) understanding.

Another option may be to have the run playbook remove those required projects from requirements.txt so that they are only used from PROJECTS or LIBS_FROM_GIT... However I'm not sure when the playbooks and moreover this might be considered bad form.

[1] https://review.openstack.org/#/c/638099/10