(cc'ing the mailing list as this is an interesting topic for all plugin developers)
I suggest to specify the dependencies in your plugin's composer.json file which is used to register it in our new plugins repository at http://plugins.roundcube.net. If the external libraries are also available as composer packages, like phpseclib, just add them to the "require" section of your composer.json file and you're done. When installing Roundcube plugins through composer, all the dependencies are downloaded and installed to vendor/xxx. Roundcube also includes composer's autoloader and therefore all classes from the external libraries are automatically available to your plugin without having to require or include anything. I hope this helps. Kind regards, Thomas On Tue, May 13, 2014 at 5:55 PM, Pi m <pim...@hotmail.com> wrote: > > Hi all, > > What is the prefered/ best way to link to external libraries in my roundcube > plugin (authres_status)? Do you have an opinion about that? > > For my plugin I would like to link to two other github projects, one is also > available through composer. For now I have added them as submodules to my > github project (not yet pushed to remote), but especially phpseclib > (https://github.com/phpseclib/phpseclib) could maybe also be interesting for > other plugins. Is there a common place to put those libraries in or should I > just create a bloated plugin that includes all those files? > > Thanks! > > Kind Rgds, Pim (aka pimlie) _______________________________________________ Roundcube Development discussion mailing list dev@lists.roundcube.net http://lists.roundcube.net/mailman/listinfo/dev
