Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency handling (chicken and egg) #51

Open
edwardbartholomew opened this issue Jun 14, 2016 · 1 comment
Open

Dependency handling (chicken and egg) #51

edwardbartholomew opened this issue Jun 14, 2016 · 1 comment

Comments

@edwardbartholomew
Copy link

As I develop a new cookbook I list the dependency cookbook foo in inventory.yml pinning it to a specific version (2.7.1). This finished cookbook I am developing does not go into minimart itself. Then I begin work on another cookbook and add its dependency bar to inventory.yml. bar uses a different version of foo (2.8.0) that explicitly described in inventory.yml so minimart mirror now errors loading bar because it breaks the foo mold. Having to explicitly list go back and edit foo's entry in inventory.yml seems awfully manual and error prone. Are there any alternatives besides listing my original cookbook in minimart or am i missing something?

-- Downloading bar 0.2.0
The dependency foo-2.8.0 could not be installed. This is because a cookbook listed in the inventory depends on a version of 'foo' that does not match the explicit requirements for the 'foo' cookbook.
Build step 'Execute shell' marked build as failure

@tapickell
Copy link
Contributor

I wonder how Supermarket handles this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants