Jordi Boggiano

Closing as nobody cared to fix it in these many years, if it is still applicable do tell and I will reopen. @dg0yt if you still have a repro case...

Ok reopening then.. What's the path you executed this in?

@Alex300 a 👍🏻 is not an answer to my question. I need to know the path you executed composer in to be able to try and reproduce.

Much like for #6816, I'd rather not add complexity here to enable sub-par use cases to proliferate. Using `>=` is a bad idea generally speaking and something we discourage as...

I would say you could use the COMPOSER_ROOT_VERSION env var to set the root package's version if you know you're building it for a given tag. Or make sure you...

If you wanna trade runtime for memory, I'd suggest maybe not optimizing the classmap at all so you have a smaller classmap? But then it's rather io cost than cpu.....

If it's about phar packaging.. Isn't this something that box (https://github.com/box-project/box) solves? We also embed the release date in Composer phars for ex by passing that in parsed from `git...

So you would set COMPOSER_ROOT_VERSION=1.0.0 COMPOSER_ROOT_REFERENCE=9c3418b8106f5e1e2b9a5b3de1a3e9b82d72d6c3 when running composer install, and would expect that the root reference is then set as if you were running in a git repo? Is...

We cannot do this as we do not retain this information at all. Packages have no reference to their source repository after they're installed.

Yeah maybe it's doable, but it would not necessarily match what happened at the time you created the lock file, so I am not sure about the value of this.