Closed moleman closed 10 years ago
tagged version created, but problem remains the same.
we have composer as a dependency, but composer itself has only alpha releases yet, so you still need an "composer/composer": "@alpha" in your requirement part when using this package.
Don't know if this issue has to do with my inability to install composer-command-integrator. It says:
magento-hackaton/composer-command-integrator 1.0 requires composer/composer * -> no matching package found.
Even tried a fork and modified the composer.json file, but without success. I have been reading carefully the instructions on magento-hackaton/magento-composer-installer. Just can't install both at the same time.
Thank you!
@blitux can you show us the used composer.json?
Yes, this is my unmodified composer.json:
{
"require": {
"magento-hackathon/magento-composer-installer":"*",
"magento-hackathon/composer-command-integrator":"*"
},
"repositories": [
{
"type": "composer",
"url": "http://packages.firegento.com"
}
],
"extra":{
"magento-root-dir": "htdocs/"
}
}
And I get this error on composer execution:
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for magento-hackathon/composer-command-integrator * -> satisfiable by magento-hackathon/composer-command-integrator[1.0].
- magento-hackathon/composer-command-integrator 1.0 requires composer/composer * -> no matching package found.
It works installing only magento-composer-installer.
Thank you!
ok, then please add the following to your require part
"composer/composer": "@alpha"
Thank you for your fast reply. Is this a bug of composer or works as expected?
I would say it works as expected.
The cause for this problem is, we need composer but composer has no stable release yet. By default composer ignores every non stable release. You can either set the minimum-stability low enough (which would affect every dependency in your project, what you dont want) or you set it like this explicit for one dependency. But you can do this only in you project composer.json. Libraries are not allowed to force non-stable releases, which is also a good and expected behavior.
Hi
This is a great module but I'm missing a tagged version of the package. The problem right now is that you either have to require "dev-master", use the @dev flag or set minimum-stability to dev in the root project (which I want to avoid). One other thing is that with a tagged version you don't have to clone the repository and Composer will cache the package on your local machine.
Thanks