Here is a followup for issue: https://drupal.org/node/2067229

Patch is on its way.

Files: 
CommentFileSizeAuthor
#2 base_profile-2081579.patch698 bytesumtj
PASSED: [[SimpleTest]]: [MySQL] 135 pass(es).
[ View ]
#1 base_profile-2081579-1.patch670 bytesumtj
PASSED: [[SimpleTest]]: [MySQL] 135 pass(es).
[ View ]

Comments

umtj’s picture

Status:Active» Needs review
StatusFileSize
new670 bytes
PASSED: [[SimpleTest]]: [MySQL] 135 pass(es).
[ View ]
umtj’s picture

StatusFileSize
new698 bytes
PASSED: [[SimpleTest]]: [MySQL] 135 pass(es).
[ View ]

Path corrected, sorry.

tstoeckler’s picture

Status:Needs review» Postponed

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 :-).

david.lukac’s picture

Issue summary:View changes

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.

tstoeckler’s picture

Status:Postponed» Closed (won't fix)

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.