Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Both Libraries API and Variables API provide support for referencing third-party code in the sites/all/libraries/ directory. Could the developer of either project comment on the different strategies used, and on the possibility of a unified approach?
Comments
Comment #1
pillarsdotnet CreditAttribution: pillarsdotnet commentedAlso see Variables API:#1017644: Compare/contrast with Libraries API
Comment #2
sunSorry, it looks like you did not read or understand the project pages. These projects have zero in common (except for having API in the name), so there's nothing that could be clarified.
Comment #3
pillarsdotnet CreditAttribution: pillarsdotnet commentedFrom libraries.module, lines 9-22
From vars.module, lines 162-170
An issue where I suggested using the Libraries API module to move third-party code from the module directory to the libraries directory, and the module author opted to use the Variables API module to accomplish the same function:
#1007454: Rudimentary libraries support
Comment #4
pillarsdotnet CreditAttribution: pillarsdotnet commentedFrom the Libraries API project page:
From the Variables API project page:
Both the code and the description appear to be different implementations of the same goal.
Comment #5
sunwell, no idea what this means, but Libraries API is the unique project/module for handling libraries.
Thus, discussion can move into #1017644: Compare/contrast with Libraries API