For consistency across the framework, the field that specifies dependencies for a package should be called "use" instead of "dependencies". This will make it consistent with the buildsystem (USE_PACKAGE) and the corto definition language (use foo/bar).
For all use declarations, a common format will be specified that indicates package, version and a prefix for the package. For example:
"use": ["foo/bar:1.2 as bar"]
This will create a dependency on foo/bar version 1.2, and will be accessible from the package as bar.
The as is a replacement of the prefix that currently is specified on the dependency package (foo/bar), which in some cases can cause name clashes. With the as syntax, packages have full control over making sure name clashes don't happen, while still allowing for short read-friendly names.
For consistency across the framework, the field that specifies dependencies for a package should be called "use" instead of "dependencies". This will make it consistent with the buildsystem (
USE_PACKAGE) and the corto definition language (use foo/bar).For all
usedeclarations, a common format will be specified that indicates package, version and a prefix for the package. For example:This will create a dependency on
foo/barversion1.2, and will be accessible from the package asbar.The
asis a replacement of theprefixthat currently is specified on the dependency package (foo/bar), which in some cases can cause name clashes. With theassyntax, packages have full control over making sure name clashes don't happen, while still allowing for short read-friendly names.