Closed h4cc closed 9 years ago
Question:
This Feature can not be managed incrementally with package:update, it has to be a single execution building the whole replacement tree again. This is needed because it has to be determined if a package does, or is still replacing another one.
Because this will be result in a large static N*M map, it could be stored inside a file in app/cache/, instead of being persisted in the database which would be more coding effort and runtime usage.
Using "replaces" information from packagist now to provide a non static solution to this problem.
There are packages from "symfony", that have their own travis configuration. For example:
http://hhvm.h4cc.de/package/symfony/monolog-bridge and http://hhvm.h4cc.de/package/symfony/monolog-bundle
In this case, if a travis configuration is given, it should be used. Maybe the composer attribute "replaces" could be used to find possible references automatically.