In the drush make documentation, I read that the optional directive [destination]
is a relative path in the runtime-defined --contrib-destination
directive. This prevents whitelisted libraries from being downloaded into paths outside the profile directory, since it seems that's what drupal.org drush make sets as the contrib-destination...?
Here's the code I'm using right now:
; Libraries
libraries[fullcalendar][download][type] = "file"
libraries[fullcalendar][download][url] = "http://arshaw.com/fullcalendar/downloads/fullcalendar-1.5.2.zip"
This downloads the fullcalendar directory into profiles/[profilename]/libraries/fullcalendar
(relative to drupal root). I'd like the folder to end up at sites/all/libraries/fullcalendar
, since that's the default location FullCalendar looks for the library (and Libraries API, too, no?).
Comments
Comment #1
dwwYeah, currently you can't do that at all. This obviously can't work in the "no-core" version of the profile tarball. I think we'd actually need to hack the d.o packaging script to support this. It has to run drush make twice. See #1455614: Packaging script doesn't allow distributions to patch core or specify a git revision for the gory details.
It seems like Libraries API and friends should be able to search in profile directories, not just sites. But, I haven't thought about it enough (or had much direct personal experience using 3rd party libs) to know if that's a problem for some reason...
Comment #2
geerlingguy CreditAttribution: geerlingguy commentedMoving over to #1472436: Allow "Path to FullCalendar" Setting to use Libraries API and marking this as closed. Using Libraries API properly should resolve this issue.
Comment #3
dwwGreat, thanks!