Closed Hywan closed 9 years ago
I thinks it's a problem regarding minimum-stability. Atoum have no tag for this branch and for this reason you need to add minimum-stability: dev
Is #9 help?
@Hywan as @vonglasow your have a min-stab
problem : hoa/test
requires àtoum/atoum@dev-extension` which is a dev package.
Requiring dev packages is rout-only in composer so here, you have two choices:
min-stab: dev
in your root composer.json
(the one where you run composer install
)atoum/atoum: *@dev
in all composer.json
requiring hoa/test
To me, both are kin of ugly but the second one is perhaps the best one (the less ugly): lowering min-stab
could lead to wrong package installation, for example if you have a dep. whit a branch-alias: 0.x-dev
and somewhere in another package you require first/lib: 0.*
, you'll likely get the dev version.
Using atoum/atoum: *@dev
will lower the risk of getting dev packages when not expected : the low min-stab
only applies to this single package.
So, we have to require atoum/atoum: *@dev
in all composer.json
files or just on hoa/test
's one?
add atoum/atoum: _@dev *_in all composer.json requiring hoa/test**
;)
It's stupid. Any workaround? Even a 0.*
tag on atoum (we have 0.0.1
but it's old). atoum is going to have a release manager (see https://github.com/atoum/atoum/issues/354) normally, so when we will have tags on atoum, we will have to update all composer.json
again (kind of a revert…). Maybe we could wait on atoum to have tags if the issue is resolved quickly?
@Hywan it's not stupid, this is how composer works and it's totally good.
Composer refuses to install non-stable package if it is not asked by the root package. This is for code security reason.
When (and if) atoum gets some tags, you'll be able to bypass this behavior but for now, the only "valid" workaround is adding the require-dev
everywhere.
Adding require-dev: hoa/test
everywhere is ok, but not dependencies of hoa/test
:-/. Do you think the issue https://github.com/atoum/atoum/issues/354 is going to be solved quickly?
@Hywan I don't think we can resolve such issue quickly: we have to define the rights/powers of release manager, and don't want atoum to become something driven by a tiny group of human working for a big company like other project have done.
We know this situation will lead to bigger problem...
@jubianchi Quickly = < 2 months for me. It's ok to not be able to run tests easily on Hoa for the next 2 months if it avoids me to do a long job and revert it few weeks later.
However, if someone is agree to do that job for me, I'm totally in.
@Hywan I hope we can fix the RM issue on atoum quickly but, as you may know, I can't (and I don't want) to take this decision only by myself.
I'll try to help you add the deps on Hoa libs this week-end ;)
up! ;)
Will up this issue soon.
Problem solved. Patches coming.
Closed by #15.
My
composer.json
file:And then:
I don't understand :-/.