Details
-
Improvement
-
Resolution: Unresolved
-
High
-
None
-
None
-
None
Description
This is already an issue with the CP version of eZ, where it is hard to bundle extensions which get enabled by default - we can currently bundle them, but the extensions are disabled.
(the hard-way to work around the problem is to ship all the extensions we want to have at startup packaged as ezp-legacy packages, but that is a feature which is going to be abandoned in favor of composer anyway)
With the possibility of using composer to declare dependency on any extension for eZ, there is a chance that these extensions get installed before the setup wizard is run. In that case, the composers script could write the list of extensions-to-install in, say, kickstart.ini, and if the setup wizard picked them up from that file, we would have acheived our goal