DOCK 3.8:How to build a release: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
1. Build desired version of [[pydock3]] Python package (e.g., build pip-installable wheel file using [[Python Poetry|poetry]]). | 1. Build desired version of [[pydock3]] Python package (e.g., build pip-installable wheel file using [[Python Poetry|poetry]]). | ||
2. Clone desired version of [[dock3]] program. | 2. Clone desired version of [[dock3]] program. | ||
3. Incorporate fruits of (1) and (2) into [[ | 3. Incorporate fruits of (1) and (2) into [[UCSF_DOCK]] repository housing legacy scripts that remain essential to established protocols (e.g., build scripts, post-processing scripts). | ||
A particular commit of the UCSF_DOCK repository becomes a particular distribution of ''UCSF DOCK'' software when the repository is assigned a tag of its [https://semver.org/ semantic version (e.g., v1.2.3)]. | |||
[[Category:DOCK 3.8]] | [[Category:DOCK 3.8]] | ||
Revision as of 08:08, 26 January 2024
This page describes how to take the three github repos, combine them, and create a tarball for public use.
1. Build desired version of pydock3 Python package (e.g., build pip-installable wheel file using poetry). 2. Clone desired version of dock3 program. 3. Incorporate fruits of (1) and (2) into UCSF_DOCK repository housing legacy scripts that remain essential to established protocols (e.g., build scripts, post-processing scripts).
A particular commit of the UCSF_DOCK repository becomes a particular distribution of UCSF DOCK software when the repository is assigned a tag of its semantic version (e.g., v1.2.3).