Thread:Talk:Requests for comment/Extension management with Composer/A way to disable extensions/reply (24)

Indeed, an explanation would be nice. I do understand the management of dependencies of composer, and I can see that wiki farm configurations must be handled in a new manner with composer. But I cannot see how one could split the extensions of a farm into two sets: commonly used extensions and individually used extensions added to the commonly used extensions. Any idea for solving the following problem?
 * wiki farm with 100 wikis
 * all wikis share a basic set of extensions
 * some wikis add further extensions which are not activated on the whole farm (example: BreadCrumbs)

Solution with LocalSettings.php
 * one directory with all extensions (including BreadCrumbs)
 * one file  (containing the  -statements for the common set of extensions)
 * individual files  (containing the  -statements for individually chosen extensions)
 * individual  files (including the files   and  )
 * adding/removing of a globally used extension:
 * adding/deletion of -statement in
 * adding/deletion of extension from the global extensions directory
 * adding/removing of a locally used extension:
 * adding/deletion of -statement in
 * adding/deletion of extension from the global extensions directory

?? Solution with Composer (assuming that in the long run all extensions will use Composer)
 * one directory with all extensions (including BreadCrumbs)
 * one file  (not including BreadCrumbs)
 * link of individual wikis to the global  file
 * ?? BUT my question is: how can individual wikis ADD BreadCrumbs to this scenario?
 * adding/removing of a globally used extension: ok - treatment via composer
 * adding/removing of a locally used extension ???

I am aware of the fact, that one could argue, that there might be dependencies between globally and locally used extensions - but adhering strictly to this credit would mean that wikis on a farm cannot be indiviualized, unless all possible combinations of individualizations are spelled out in separate  files and each wiki links to a different   file - which makes the idea of maintaining a wiki farm rather odd

PS I have chosen BreadCrumbs as an example of an extension which changes the appeareance of a wiki if it is activated

Does anybody have a solution for this scenario? Does composer have an inheritance mechanism?