>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #1241704. --> Reported by: [rfay](https://www.drupal.org/user/30906) >>> <p>I think <a href="http://drupal.org/project/project_dependency">Project Dependency</a> is ready to go on Drupal.org.</p> <p>Project Dependency replaces the old project_info module which was hotpatched onto d.o about 2 years ago.</p> <p>There are many reasons we've wanted dependency detection and enumeration, but the most important immediate one is that testbots can download module dependencies. Many, many projects have not been able to run tests (Views, Commerce) because they have external dependencies. Now that information can be delivered to the testbots, and the testbots can download the dependencies.</p> <h3>Deployment:</h3> <ul> <li>Deploy <a href="http://drupal.org/project/project_dependency">Project Dependency</a> </li><li>Deploy the latest <a href="http://drupal.org/project/project_issue_file_test">Project Issue File Test</a> </li><li>Deploy Project module *or* just the patch in <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/project/issues/1200486" title="Status: Closed (fixed)">#1200486: Invoke hook_project_release_create_package() when a package is being created</a></span> </li><li>Configure Project Dependency and build the git checkouts for all the projects. This is a straightforward drush command. The complete setup description is in in the <a href="http://drupalcode.org/project/project_dependency.git/blob_plain/refs/heads/6.x-1.x:/README.md">README.md</a> in the project folder. </li></ul> <h3>Risks</h3> <ul> <li>Performance: at hook_project_release_create_package() time: It takes a second or two to create the dependencies. It feels really fast when you do it by hand. It only happens when a new package is rolled, so I don't expect it to be hugely expensive. </li><li>Performance: At test dependency generation time: Each test to be sent to qa.drupal.org requires searching the module's tables for dependencies. This seems quite fast, and is only encountered when preparing a test. I don't expect it to be a problem. </li><li>I don't know of any impacts, performance or otherwise, on any other subsystems. </li></ul> <p>The issue where this was developed: <span class="drupalorg-gitlab-issue-link project-issue-status-info project-issue-status-7"><a href="https://www.drupal.org/project/project_dependency/issues/102102" title="Status: Closed (fixed)">#102102: Parse project .info files: present module list and dependency information</a></span>. </p>