Jordi Boggiano

Do you have junctions/symlinked dirs within the project which point to broken/missing directories? Otherwise getRealPath should work.. But yes I guess we could just always check and if it fails...

@HenkPoley I'll fix this now but I'd still appreciate if you could do what I asked above so we can figure out more info about this: > Could you run...

Yeah that seems more like something to report to flex really, I don't know why they use such constraints instead of ^6.3.

But I see your point, we upgrade 2.* to ^2.4, so maybe we should also upgrade minor wildcards.. However, switching to ^6.3 would change the meaning as it allows 6.4+...

Ignoring unbound version constraints I'd rather not even allow this, there is no good reason for this IMO. As for checking for packagist:false, I guess you could hook into the...

Composer is a dependency manager though, we have a few helpful things like that which can be convenient for simple things, but if you need a complex CLI IMO it...

This would require we have git clones of repos just to even start an install though in case of mismatches, which definitely increases complexity quite a bit for a use...

@cuchac I'd like to understand more about the use case.. Why is changing the shared composer.json breaking everything? Why would you update the base composer.json and not update the dependencies?...

Ok I see.. That's kinda the problem with this merge plugin approach, vs having the "base" project as a proper dependency that would be updated whenever you actually update it,...

Yeah I guess we could do that, sounds reasonable although a little work for not much value IMO as the lock file should not really be opened/edited.