Try to query against the d.o. packaging white-list (not sure how to do this) so that defaults based on white-listed paths can be added or at least issues pointed to for some idea as to how to get this info.

If this isn't possible (quite likely) then start generating preferred ones based on those commonly included in distros. Many of these libraries are locked in time but hosted elsewhere for consistency reasons. Build a default definition as well as ways for others to define and modify the list.

Form of the array could follow drush make file convention. If it isn't defined in the array then it defaults to the current guessing method w/ a todo.

Comments

btopro’s picture

btopro CreditAttribution: btopro commented
Status: Active » Fixed

This is in dev now and there's a new API for defining library location information that previously was just "TODO". This comes with some built in for popular libraries like plupload, masonry, oauth, ckeditor, and bootstrap among others. We will take requests for adding to the main library via the issue queue (similar to packaging white-list) although it's easy enough to add your own in via the same hooks. It also takes into account local vs non-local packaging as to where the script can be included. The hope is most migrate to white-list supported but somethings (like bootstrap) unfortunately can never migrate to the d.o. packaging script due to licensing.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.