Closed (duplicate)
Project:
Libraries API
Version:
7.x-2.1
Component:
Code
Priority:
Minor
Category:
Feature request
Assigned:
Reporter:
Created:
13 Sep 2012 at 13:34 UTC
Updated:
3 Nov 2014 at 15:57 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
tekante commentedPatch is attached. Will mark this as needs review just so the maintainer can take a quick look but I suspect that since this is a patch dependent on a patch this should likely be closed as a won't fix or as designed (pending real support of inherited profiles in core).
Comment #2
tekante commentedCorrection of patch naming and status change. Patch is identical but improper name on previous version would make it hard to track back to this issue from a make file.
Comment #3
tstoecklerPatch looks good, but I'm setting to postponed until the core issue gets in.
Comment #4
pmelab commentedRecreated the patch for libraries version 2.1
Comment #5
dagomar commentedThe patch in #4 goes with patch #25 here: #1356276-25: Allow profiles to define a base/parent profile. However, after that the function drupal_system_listing_profile was removed from the patches. So, #4 will now result in a WSOD (call to undefined function).
To make matters more complicated, the referred issue was split up to allow D7 and D8 development to live independently from one another. So, I have created a new patch that takes into account the latest available patch (surprise, also by me) in the newly created issue here: #2067229-41: Allow install profiles to declare base profiles for Drupal 7
The patch basically lifts the drupal_system_listing_profile from the old patch and adds it to the libraries module as libraries_system_listing_profile.
Comment #6
tstoecklerMarking duplicate of #2081579: Base profile support