Dependency Management: Composer

[MichaelC]

I've tried running composer.phar on Windows in phpBB directory and ran into this problem:

Code: Select all

  - Installing symfony/config (v2.1.0-RC1)
    Downloading: connection...


  [Composer\Downloader\TransportException]
  The "http://nodeload.github.com/symfony/Config/zipball/v2.1.0-RC1" file could not be downloaded (HTTP/1.1 404 Not Found)

Travis had the problem earlier, the url it was using was incorrect for some reason.

[brunoais]

I'm having this problem:

Code: Select all

$ php ../composer.phar install
This dev build of composer is outdated, please run "../composer.phar self-update
" to get the latest version.

$ php ../composer.phar self-update
Updating to version 99b7ab4.
    Downloading: 100%
	
$ php ../composer.phar install
Loading composer repositories with package information
Installing dependencies from lock file
  - Updating symfony/event-dispatcher (2.0.x-dev 69f86e4 => v2.1.0-RC1)
    Checking out v2.1.0-RC1



  [RuntimeException]
  Failed to clone http://github.com/symfony/EventDispatcher via git, https an
  d http protocols, aborting.

  - git://github.com/symfony/EventDispatcher
    fatal: No such remote 'composer'

  - https://github.com/symfony/EventDispatcher
    fatal: No such remote 'composer'

  - http://github.com/symfony/EventDispatcher
    fatal: No such remote 'composer'

install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-custom-installers] [--no-scripts] [-v|--verbose] [-o|--optimize-autoloader]

Not until this is solved I cannot do QA work properly. I can only do code checks.

[EXreaction]

RFC to include vendor: viewtopic.php?f=108&t=43563

[Arty]

@brunoais Try files in attachment. Unpack it to phpBB directory.

[brunoais]

Which steps did you take to get those files?

[Arty]

Which steps did you take to get those files?

Updated old vendor directory instead of creating new one.

[brunoais]

Where were those files you used to update, then?

[imkingdavid]

Where were those files you used to update, then?

He had already done the composer install command. Apparently all he did was run the composer update command with a non-empty vendor directory. So the files he used to update were in the vendor folder from before.

[MichaelC]

Where were those files you used to update, then?

He had already done the composer install command. Apparently all he did was run the composer update command with a non-empty vendor directory. So the files he used to update were in the vendor folder from before.

No, php ../composer.phar update changes the .lock file, you should only ever use php ../composer.phar install unless you need to update the version used because your developing a feature. php ../composer.phar install looks to see if there have been any differences between your packages.json in your vendor/ and the composer.lock and if so then it updates any relevant libs to the version specified in the composer.lock. Then if there isn't any packages.json it will install all dependencies.

[shoes22]

So if I'm understanding correctly, use of Symfony/Composer will be phased out by the time an alpha or beta of 3.1 is released, correct?
How exactly is this going to work? I'm just curious because right now I see a LOT of code being tied into it. Especially functions related stuff.
And after a quick browse of this thread I found that including the /vendor folder in develop was rejected as an RFC.