Extension dependencies

Note: If your extension dependencies have their own dependencies it’s best if each extension only includes it’s immediate dependents and let the dependencies cascade until they have all been satisfied; i.e. if your extension requires X which requires Y which requires Z only declare your dependence on X and have Y declare it’s dependence on Z and so on. While extension bundling is for site maintainers, extension dependencies are for extension authors. As you can probably guess it lets you tell Ray about your extension’s dependencies. All you need is a <code>dependency.yml</code> file in the root directory of your extension. Here’s an example dependency file: <pre><code>- extension: my_extension_helpers</code></pre> You can list as many dependencies as you need and they can include gems as well as other extensions. In the case of extensions you may also use the <code>hub</code> option if you depend on a forked version of a repository. <pre><code>- extension: this_extension_helps_a_ton hub: extension_forker - extension: some_other_voodoo - gem: this_one - gem: that_too</code></pre> The absence of support for plugin dependencies is intentional. You are much better off adding plugins to your extension as <code>git</code> submodules and letting Ray deal with them during the normal installation of your extension. As an added bonus your plugin dependencies will also be recognized and respected by Radiant’s built-in <code>script/extension install</code>. Note: <code>dependencies.yml</code> is an acceptable file name and <code>.yaml</code> is an acceptable extension. 2009-11-08T08:37:30-08:00 118970 extension-dependencies

34113

2009-04-12T13:48:49-07:00

7944