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

Root Package Versioning and 'child' packages #7

Open
jeffturcotte opened this issue Feb 5, 2014 · 0 comments
Open

Root Package Versioning and 'child' packages #7

jeffturcotte opened this issue Feb 5, 2014 · 0 comments

Comments

@jeffturcotte
Copy link
Member

Currently, If you were to add a new major version to a root/framework package where your directory structure changed, your packages supporting that framework cannot specify the version of the package they support.

The best "workaround" is currently to override the framework name in your root package config for the new version. This means that no new root package repository would be needed and your child packages can simply add the new framework name to their map.

I think the solution above is probably adequate, but we should at least explore the idea of specifying project/framework versions in the child package. It's most likely possible to take advantage of the functionality provided by \Composer\Package\Version\VersionParser in supporting this.

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

No branches or pull requests

1 participant