Closed Rarst closed 11 years ago
This is because of how composer-installers handles packages. Basically, they seem to have "reserved" ANY type that starts with wordpress-
and will throw an exception if it's not one of the types they have allowed.
I'm not sure what the best course of action is, but it seems to me we have two possibilities:
wordpress-core
to something like wp-core
or core-wordpress
Ok, I opened an issue at composer/installers#98 asking them to stop hijacking wordpress-*
types. We'll see where it goes, if anywhere.
Install fails if core package, using core installer, is used alongside other package, using
composer/installers
.composer.json
Install log ends up in