This tool helps you to import tools and workflows from other sources for use in your own workflow.
# Setup
It is highly recommended to setup virtual environment before installing `cwldep`:
```
virtualenv -p python2 venv # Create a virtual environment, can use `python3` as well
source venv/bin/activate # Activate environment before installing `cwldep`
```
Install from source:
```
git clone https://github.com/common-workflow-language/cwldep.git # clone cwldep repo
cd cwldep # Switch to source directory
python setup.py install
cwldep -h # Check if the installation works correctly
```
# Adding file dependencies
```
cwldep add myfile.cwl https://raw.githubusercontent.com/common-workflow-language/workflows/master/tools/samtools-faidx.cwl
```
This will download the CWL file *and its dependencies* to `raw.githubusercontent.com/common-workflow-language/workflows/master/tools`
Include it in your workflow as a relative file reference:
```
steps:
step1:
in: ...
out: ...
run: raw.githubusercontent.com/common-workflow-language/workflows/master/tools/samtools-faidx.cwl
```
# Changing the install target
```
cwldep add --install-to samtools myfile.cwl https://raw.githubusercontent.com/common-workflow-language/workflows/master/tools/samtools-faidx.cwl
```
# Using archives
You can also import archives (.tar.gz, .tar.bz2, and .zip):
```
cwldep add myfile.cwl https://github.com/common-workflow-language/workflows/archive/draft2.tar.gz
```
This will download and extract to the local directory `github.com/common-workflow-language/workflows/archive`
# Using git upstream
You can also import git repositories:
```
cwldep add myfile.cwl https://github.com/common-workflow-language/workflows
```
This will clone into the local directory `github.com/common-workflow-language/workflows`
```
cwldep add --set-version=draft-2 myfile.cwl https://github.com/common-workflow-language/workflows
```
# Installing dependencies
This will install any dependencies listed in `myfile.cwl`
```
cwldep install myfile.cwl
```
# Checking if upstream dependencies have changed
This will report if the upstream dependencies listed in `myfile.cwl` have changed
```
cwldep check myfile.cwl
```
# Updating dependencies
This will install updated dependencies:
```
cwldep update myfile.cwl
```
# Deleting unreferenced dependencies
This will delete any dependencies listed in the ".dep.lock" file that are not referenced by `myfile.cwl`.
```
cwldep clean myfile.cwl
```
Metadata
Release files for cwldep 1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cwldep-1.0-py3-none-any.whl | Python 3 | none | any | Details for cwldep-1.0-py3-none-any.whl |
Release files / cwldep-1.0-py3-none-any.whl
| Download URL | cwldep-1.0-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9af635874ea0f0f6637f153448b7ee3c9a0048a76b7fa3f43ad56d6130891da4
|
|
BLAKE2b-256 checksum How to use checksums |
e2203ccc6d9033ebaef057512c3f8d085ed95cb2fc89e408afc4536eb8d3ba32
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for cwldep 1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.