On Wed, Jun 4, 2014 at 9:53 AM, Tyler Romeo tylerromeo@gmail.com wrote:
Here is the solution: rather than using Composer as a package management system when, in reality, it is a dependency management system, we use Composer to properly maintain core, and then do one of the following: 1) implement our own extension installation system from scratch, or 2) change and/or extend Composer so that it supports a plugin system. I personally recommend the latter, and there are upstream bug reports open concerning it.
As a temporary workaround, maybe we could create extensions/composer-example.json which could be used for extension registration by running composer in that directory?