Initial version of "depends"
































1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
## # depends:

Lists other plugins or language/system libraries which the current plugin requires:

    # depends: corefuncs, json_io

Typically it just lists other plugin basenames. And it's a strong indicator that those must be enabled alongside or prior.

  * It's a list of local URNs.

  * The recommended default is "depends" and not "require", for compatibility with the Debian packaging spec.

  * Also it does not strictly need to enforced strictly in each application. It's more of a recommendation and user-visible field. In dynamic langauges plugins can soft-detect missing dependencies mostly.


## System/language dependencies

This is quite informal / not fixated, but non-plugin dependencies are usually denominated with `type:name` like:

  * `# depends: bin:imagemagick` for binaries
  * `python:lyxml` for language modules
  * Or `sys:amd64` for the architecture.
 * And `deb:

## Related fields

Depending on complexity other fields might be used alongside:

  * `# provides:`
  * `# conflicts:`
  * `# suggests:`