Voting starts in March for the Drupal Association Board election.
Here is a followup for issue: https://drupal.org/node/2067229
Patch is on its way.
Path corrected, sorry.
I'd surely love to add this feature. But I don't see much value in adding this until the Drupal core issue is in. So marking postponed, unless you can make a compelling case :-).
Definitely +1 for this one. We work with install profiles most of the time and having modules support 'base' profiles would be a great advantage.
So I don't see this getting into core in any way, so closing this one.
What I would be open to is the following: If someone is able to implement this functionality as a *module* (no idea if that possible, but just assuming that it is for now), then I would totally be fine doing a module_exists() check in libraries_get_libraries() in order to support base profiles. If that happens, please do re-open this issue.
I really think base profiles are a pretty cool feature and I would love to have them in core, but that's not something I can control, and since they currently aren't I don't think it makes sense for Libraries API to be "forward-supporting" of some very distant core feature.
Marked #2733787: Allow install profiles include libraries from their base profile as duplicate.
Re-posting the patch from https://www.drupal.org/node/2733787 in case someone else is looking for a patch that isn't three years old.
We included a small alter in the libraries module to allow us to include new library locations via hook_libraries_search_path_alter(). While adjusting the base profiles to inherit libraries properly would be ideal, this solution is small enough for our implementation.
Drupal is a registered trademark of Dries Buytaert.