Should we recursively check all packages for `drupal-libraries` properties?

[balbuf]

• This would allow modules, etc. to require this plugin and libraries would automatically be installed with no additional user action required
• In the case of conflicting files using the same library name, the conflict would be resolved by declaring the desired library in the root package

[ericmulder1980]

Would a library dependency from an installation profile benefit from this? I am in the process of creating an installation profile for one of my customers and i am using composer to gather all project dependencies.

The project consists of the following:

1. Installation profile
2. Corporate theme
3. Project blueprint

The project blueprint combines the installation profile and corporate theme and offers the possibility to add extra modules/libraries that are not necessary for all projects created with this installation profile.

The installation profile can depend on a few libraries such as colorbox or dropzone. I want to add the requirements to the profile. Currently i can only force the placement of these libraries in the correct folders by adding the "drupal-libraries" part to the project blueprint. It would be awesome if i could manage this from the installation profile and allow the "library-directory" to be overridden in the project blueprint and also add additional libraries that are not part of the installation profile.