Package dependencies may be included in either packages.yml
or dependencies.yml
#6029
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Preview
What are you changing in this pull request and why?
db users have (4) choices as it relates to
packages.yml
anddependencies.yml
files:packages.yml
nordependencies.yml
packages.yml
dependencies.yml
packages.yml
anddependencies.yml
** If both files exist, then only one of them can define the
packages:
key (i.e.,packages.yml
!).Side note
To me, the most simple instructions would be:
packages.yml
dependencies.yml
That would keep things very understandable without needing to get into the details of caveats like Jinja, private packages, etc.
So I opened #6129 with this suggested simplification.
Checklist