Are composer global packages installed correctly?

[natanmoraes]

When I run composer global require drupal/coder, the vendor files are installed in ~/.config/composer.

See build screenshot:

I was expecting they would be installed under ~/.composer.

Is this by design?

My .travis.yml file:

language: php
sudo: required
dist: trusty

php:
  - 5.6

install:
  # Remove xdebug to make composer faster.
  - phpenv config-rm xdebug.ini
  # add composer's global bin directory to the path
  # see: https://github.com/drush-ops/drush#install---composer
  - export PATH="$HOME/.config/composer/vendor/bin:$PATH"

  # Install PHP_CodeSniffer and Drupal config
  - composer global require drupal/coder
  - phpcs --config-set installed_paths ~/.config/composer/vendor/drupal/coder/coder_sniffer

before_script:
  # This slows things down but it ensures all remote branches are fetched.
  - git config remote.origin.fetch "+refs/heads/*:refs/remotes/origin/*"
  - git fetch --unshallow
  - git fetch origin

script: ./scripts/travis-build.sh

[MarkVaughn]

Any luck with this? Trying the same thing with global install

[BanzaiMan]

Do you have a build log URL that shows the problem you are describing here?

[MarkVaughn]

At first I the install had
- composer global require "squizlabs/php_codesniffer=*"
and the script had
- phpcs --standard=custom_ruleset.xml --encoding=utf-8 -np src
Which resulted in

phpcs: command not found

After researching a bit more I changed the install bit to

- pear install pear/PHP_CodeSniffer
- phpenv rehash

Which ended up working fine.
I'm assuming composer global require doesn't work because the ..pathto/.composer/vendor/bin is probably not in the path.

[BanzaiMan]

Do you have a build log URL that we can take a look at, so that we can determine if there is anything for us to fix?

[MarkVaughn]

The log is on the .com version of travis. But if you got admin access: build id is 42453136, install on line 398, error on line 453 the commands are as mentioned in my previous post

[BanzaiMan]

@MarkVaughn Thanks for the info.

Your log indicates:

Changed current directory to /home/travis/.composer

which is different from what @natanmoraes wrote originally.

In addition, it is not clear from your log how you are invoking composer commands; it is also not clear where phpcs is installed by Composer, or whether or not the directory in question is on your $PATH.

I also see that the build 2759 on the same PR fixed the issue. How was it fixed?

[MarkVaughn]

As mentioned in my previous post, this is the command:
composer global require "squizlabs/php_codesniffer=*"

But i fixed it by switching to

pear install pear/PHP_CodeSniffer
phpenv rehash

Essentially ditching global composer for pear.

When doing global composer installs the executables would be located in /home/travis/.composer/vendor/bin which I'm assuming is not in the $PATH

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

[robbieaverill]

Hi team, I've just noticed this happening on some of our builds as well (switching from ~/.composer to ~/.config/composer). @BanzaiMan do you know why this changes? I'm happy to update all of our Travis config files, but hopefully it won't change back again to the former path =)

[raoulduke]

Having the same issue. Any global composer installation results in ~/.config/composer as the installation directory. It can be seen in the output after your command:

Changed current directory to /home/travis/.config/composer

[robbieaverill]

The output of composer global --help says:

Use this command as a wrapper to run other Composer commands
within the global context of COMPOSER_HOME.

You can use this to install CLI utilities globally, all you need
is to add the COMPOSER_HOME/vendor/bin dir to your PATH env var.

COMPOSER_HOME is c:\Users\AppData\Roaming\Composer on Windows
and /home//.composer on unix systems.
If your system uses freedesktop.org standards, then it will first check
XDG_CONFIG_HOME or default to /home//.config/composer

If the Travis PHP images have changed distro recently then that would explain the change

[raoulduke]

@robbieaverill I'm used to /home/<user>/.composer on unix systems, but I'm assuming from that output it means Travis is using the freedesktop.org specifications. Might be worth noting this in the build environment docs.

[robbieaverill]

composer global exec [binaryname] [args] looks like a promising option to avoid needing to specify the path at all, but it doesn't seem to work for me on my laptop =(

[raoulduke]

@robbieaverill Use composer global exec -- "your command and options".

Example on my vagrant box:

$ composer global exec -v --  "phpcs -n --standard=PSR2 /home/vagrant/code/test"
Changed current directory to /home/vagrant/.composer
> __exec_command: phpcs -n --standard=PSR2 /home/vagrant/code/test

[robbieaverill]

Ah I see, I had to make it verbose to get output. So this could be a decent replacement for running global binaries via the composer global install path (which is variable)

[aphofstede]

This worked for me: export PATH="$PATH:$HOME/.config/composer/vendor/bin:$HOME/.composer/vendor/bin"