Debian solving Drupal's third-party library challenge
While these policies may seem onerous at first glance, it turns out there is another project with a written guarantee to provide third-party code in a form that meets the expectations of Drupal and does so in a way that completely automates all that tedious effort into one-click oblivion. I'm talking about the Debian GNU/Linux operating system.
Drupal's libraries module
The module has been available in Debian for almost a year and has recently been provided in the wheezy-backports distribution for people running the stable version of Debian.
Using the module in practice
I've recently uploaded JSCommunicator to Debian and wanted to provide a convenient way for people to get it in Drupal.
|Third-party library||Library itself||Drupal module, packaged|
If you explore the package details in Debian's package catalog you will notice that each package depends on the other packages it requires.
Debian's package management utility, apt-get, can transitively resolve all the relationships between this set of packages. In fact, on a newly built server, you can simply run the command:
apt-get install drupal7-mod-jscommunicator
Libraries API in Drupal 8
Contrary to an earlier version of this blog, the libraries module is not joining the core in Drupal 8 however its use has been strongly encouraged for any new modules submitted through the Drupal community approval process. This means there will be further opportunity for Drupal users to consolidate on their use of Debian to completely automate the management of all third-party libraries and modules throughout their Drupal system(s).