Changeset View
Changeset View
Standalone View
Standalone View
bin/install
#!/usr/bin/env bash | #!/usr/bin/env bash | ||||
pip install $(./bin/pip-swh-packages --with-testing) "$@" | # Usage: bin/install [PIP_INSTALL_OPTION..] | ||||
ardumont: pifpaf can go away now (can be cleaned up later though) | |||||
PREREQUISITES="pre-commit flake8 pifpaf tox wheel mypy" | |||||
pip install --upgrade pip "$@" | |||||
pip install $PREREQUISITES "$@" | |||||
bin/pip-swh-packages --with-testing | \ | |||||
while read pkg_spec ; do | |||||
pip install $pkg_spec | |||||
Not Done Inline ActionsI'm also wondering whether we should add checks on runtime dependencies (the ones that could not be dealt with pip and which are referenced in the docs [1]). A simple check and warning if missing. [1] https://docs.softwareheritage.org/devel/developer-setup.html#install-required-dependencies ardumont: I'm also wondering whether we should add checks on runtime dependencies (the ones that could… | |||||
Done Inline ActionsNot a bad idea, but they are all system dependencies, I have no idea if there is a reasonable way to check for their presence without having to discriminate debian/redhat/etc. (which clearly we do not want to do). I've took care of pre-commit though, but I think it's needed at bin/update time (which happens before), so it's not really helping either. zack: Not a bad idea, but they are all system dependencies, I have no idea if there is a reasonable… | |||||
done |
pifpaf can go away now (can be cleaned up later though)