24 May
2007
24 May
'07
6:55 p.m.
aps to address this concern, we could create a dedicated module that simply provides the third party library in question and little or no additional functionality as required by drupal. The the modules that depend on it can do just that in the info files. Avoids duplication and centralizes the management and ability to audit for security issues too boot.
This is the approach Jeff Robins has taken with his jQuery_update and jQuery_interface modules, and I think it works very well. This approach leverages Drupal's project versioning and dependency systems to keep the 3rd party (GPL) code insync with the Drupal code, and simplifies instillation.