Databases
StackOverflow2013
Postsdbo
POWhy updating of dependencies in composer is so slow?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy updating of dependencies in composer is so slow?
    primarykey
    data
    text
    <p>I am using composer (<a href="http://getcomposer.org/">http://getcomposer.org/</a>) to manage installed bundles in the <code>Symfony2</code> (symfony v 2.1.3). Version of the composer is <code>de3188c</code>. </p> <p>I have problem that when I add new bundle into the composer.json and execute it the time to show messages about Updating dependencies and next downloading them all is very low. </p> <p>I have this data in the composer.json (see below) and the executing time is approximately 20 MINUTES!!! The internet connection is fast enough I can download big files very fast...</p> <p>Is there any trick to make it faster?</p> <pre><code>{ "name": "symfony/framework-standard-edition", "description": "The \"Symfony Standard Edition\" distribution", "autoload": { "psr-0": { "": "src/" } }, "require": { "php": "&gt;=5.3.3", "symfony/symfony": "2.1.*", "doctrine/orm": "&gt;=2.2.3,&lt;2.4-dev", "doctrine/doctrine-bundle": "1.0.*", "twig/extensions": "1.0.*", "symfony/assetic-bundle": "2.1.*", "symfony/swiftmailer-bundle": "2.1.*", "symfony/monolog-bundle": "2.1.*", "sensio/distribution-bundle": "2.1.*", "sensio/framework-extra-bundle": "2.1.*", "sensio/generator-bundle": "2.1.*", "jms/security-extra-bundle": "1.2.*", "jms/di-extra-bundle": "1.1.*", "doctrine/doctrine-fixtures-bundle": "dev-master", "webignition/doctrine-migrations-bundle": "dev-master" }, "scripts": { "post-install-cmd": [ "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::buildBootstrap", "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::clearCache", "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installAssets", "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installRequirementsFile" ], "post-update-cmd": [ "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::buildBootstrap", "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::clearCache", "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installAssets", "Sensio\\Bundle\\DistributionBundle\\Composer\\ScriptHandler::installRequirementsFile" ] }, "minimum-stability": "dev", "extra": { "symfony-app-dir": "app", "symfony-web-dir": "web" } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USReuben L.
    1. USMyth Rush
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhy updating of dependencies in composer is so slow?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhy updating of dependencies in composer is so slow?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhy updating of dependencies in composer is so slow?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWhat you can do - is to specify needed tag (instead of 2.1.* use 2.1.1 f.e.)
      singulars
      1. POWhy updating of dependencies in composer is so slow?
      1. USVitalii Zurian
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload