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 issue #605

Closed
oldskool opened this issue Oct 24, 2015 · 3 comments
Closed

Dependency issue #605

oldskool opened this issue Oct 24, 2015 · 3 comments

Comments

@oldskool
Copy link

I have an issue in my dev environment.

The core repo seems to be a dependency of the "flarum" repo as well. This is causing me to have both:

/vagrant/flarum/vendor/flarum/core

As well as my own development files (the submodule) in:

/vagrant/flarum/flarum/core

Composer seems to "prefer" the version in the /vagrant/flarum/vendor dir over my own files, hence it's not testable (since it's not using my files but the latest repo files instead).

Is there an easy way to tell composer to ignore the "root level" files and use my files instead?

@kirkbushell
Copy link
Contributor

When developing, setup your own package and just set the dependency.

@tobyzerner
Copy link
Contributor

composer remove flarum/core, and then use franzliedke/studio to load your local copy of flarum/core.

@luceos
Copy link
Member

luceos commented Nov 20, 2015

or use repositories - path to overrule that flarum/core is a remote dependancy, it will load a local folder instead, see: https://getcomposer.org/doc/05-repositories.md#path

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

4 participants