1
0
Fork 0

Clarify global packages and what global cmd does, fixes #4495, closes #4525

pull/4757/head
Jordi Boggiano 2016-01-09 19:08:22 +00:00
parent 969263944c
commit 814e09c456
2 changed files with 7 additions and 3 deletions

View File

@ -9,8 +9,9 @@ for you.
Composer is **not** a package manager in the same sense as Yum or Apt are. Yes, Composer is **not** a package manager in the same sense as Yum or Apt are. Yes,
it deals with "packages" or libraries, but it manages them on a per-project it deals with "packages" or libraries, but it manages them on a per-project
basis, installing them in a directory (e.g. `vendor`) inside your project. By basis, installing them in a directory (e.g. `vendor`) inside your project. By
default it will never install anything globally. Thus, it is a dependency default it does not install anything globally. Thus, it is a dependency
manager. manager. It does however support a "global" project for convenience via the
[global](03-cli.md#global) command.
This idea is not new and Composer is strongly inspired by node's This idea is not new and Composer is strongly inspired by node's
[npm](https://npmjs.org/) and ruby's [bundler](http://bundler.io/). [npm](https://npmjs.org/) and ruby's [bundler](http://bundler.io/).

View File

@ -225,6 +225,9 @@ The global command allows you to run other commands like `install`, `require`
or `update` as if you were running them from the [COMPOSER_HOME](#composer-home) or `update` as if you were running them from the [COMPOSER_HOME](#composer-home)
directory. directory.
This is merely a helper to manage a project stored in a central location that
can hold CLI tools or Composer plugins that you want to have available everywhere.
This can be used to install CLI utilities globally and if you add This can be used to install CLI utilities globally and if you add
`$COMPOSER_HOME/vendor/bin` to your `$PATH` environment variable. Here is an `$COMPOSER_HOME/vendor/bin` to your `$PATH` environment variable. Here is an
example: example: