It really depends on the licensing of the library. If the library is licensed under GPL family licenses, you can ship it with your module. Otherwise, you will have to put the library in sites/all/libraries.<div><br></div><div>
See these links:</div><div>Related issue - <a href="http://drupal.org/node/1294060">http://drupal.org/node/1294060</a></div><div>More info - <a href="http://drupal.org/licensing/faq#q7">http://drupal.org/licensing/faq#q7</a><br>
<br><div class="gmail_quote">On 5 December 2011 17:29, webmaster <span dir="ltr"><<a href="mailto:fairsayan@gmail.com">fairsayan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi folks,<br>I'm creating a new Drupal module for the connection to
Google Calendar using Google API. I know the main aim of Drupal
libraries is for CSS and JS instead of google-api-php-client is mainly a
PHP library.<br>
Do you suggest to me to put google-api-php-client files in
sites/all/libraries anyway or to ship google-api-php-client in my
module?<br>Thanks,<br>Fair
</blockquote></div><br></div>