multiple default_sources should have a configurable priority for automatic preferred_for behavior #42
Labels
Aspect: UX
How users feel interacting with the project, focusing on function, ease-of-use and accessibility.
Triage: Confirmed
Indicates and issue has been confirmed as described.
Triage: Feature Request
Indicates an issue requesting new functionality.
Type: Design Proposal
Community survey of a proposal.
Type: Enhancement
Adds new functionality.
The default behavior should not change, but users really want to be able to say "use all my
:chef_repo
cookbooks first, then use:supermarket
second, and i don't want to tell you that my version ofbuild-essentials
should always take priority"Right now that looks something like:
The new DSL code should behave the same way so that if the
:chef_repo
takes priority over:supermaket
then the presence of abuild-essential-0.0.1
cookbook in the:chef_repo
would take precedence over any version ofbuild-essential
in supermarket and there would be no crazy merging of actual versions -- presence of any version in a higher priority repo would knock out all versions in a lower priority repo.The text was updated successfully, but these errors were encountered: