8000 [DX] Using `composer ...` or `php composer.phar ...` · Issue #4170 · symfony/symfony-docs · GitHub
[go: up one dir, main page]
Skip to content

[DX] Using composer ... or php composer.phar ... #4170

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wouterj opened this issue Aug 23, 2014 · 13 comments
Closed

[DX] Using composer ... or php composer.phar ... #4170

wouterj opened this issue Aug 23, 2014 · 13 comments
Labels
DX hasPR A Pull Request has already been submitted for this issue.

Comments

@wouterj
Copy link
Member
wouterj commented Aug 23, 2014

The official download page uses the composer ... command, while the docs are using php composer.phar ....

If you follow the complete installation instructions in the Composer docs, you end up with composer on Windows and Unix. If you simply download the phar in your project, you end up using php composer.phar.

What should we use?

@Seldaek maybe you have an opinion about this?
@javiereguiluz
Copy link
Member

As you tagged the issue as needs comments, I'll add my comment even if I'm not @Seldaek.

I'm strongly in favor of the Composer global installation and thus, composer should be the only way to execute Composer. Symfony documentation should be updated accordingly.

@stof
Copy link
Member
stof commented Aug 23, 2014

For reference, see composer/composer#3125 about documenting the global installation first in the composer doc

@wouterj wouterj mentioned this issue Aug 23, 2014
Closed
@xabbuh xabbuh mentioned this issue Aug 23, 2014
Merged
@fabpot
Copy link
Member
fabpot commented Aug 23, 2014

👍 for installing Composer globally.

@javiereguiluz
Copy link
Member

What do you think about giving a huge push to global Composer installation by submitting issues or pull requests for the documentation of all major frameworks?

@xabbuh
Copy link
Member
xabbuh commented Aug 23, 2014

👍 for this suggestion.

@weaverryan
Copy link
Member

Following up on composer/composer#3125, the PR at composer/composer#3130 would make it so that the current composer installation method adds a global composer command (even to Windows).

So I'm +1 for this as well, but contingent on seeing either the PR merged, or at least https://getcomposer.org/download/ showing instructions on how to do the global install. If we had this, then I think it's an easy sell to go around to all the libs and change composer.phar to composer.

@raulfraile
Copy link
Contributor

👍 for installing Composer globally in instructions for Symfony, third-party bundles and major frameworks

@aferrandini
Copy link
Contributor

👍 for installing Composer globally in Symfony instructions.
I think that could be add a remember of how to update Composer.

@cordoval
Copy link
Contributor
cordoval commented Sep 4, 2014

i think in terms of practical terms, is better to move a phar to the PATH and rename it rather than install tools on a composer --global install. So if it is globally in the sense of global i am 👎 but if it is phar renamed to user PATH then 👍

@xabbuh
Copy link
Member
xabbuh commented Sep 5, 2014

@cordoval This issue is about where to install Composer not about how and where to install packages with Composer.

@Seldaek
Copy link
Member
Seldaek commented Sep 7, 2014

FWIW I'm all for pushing for global installs too. I'll take a look at the above linked issues.

That said, in composer docs I tend to use php composer.phar ... in instructions because I figure those capable of doing a global install are also capable of mentally translating that to composer ..., while the newcomer styles will be less confused if it just works by copy pasting commands.

@acrobat
Copy link
Contributor
acrobat commented Oct 17, 2014

👍 global install looks like the best solution to me

@xabbuh
Copy link
Member
xabbuh commented Oct 19, 2014

How do we handle this now?

@wouterj wouterj added hasPR A Pull Request has already been submitted for this issue. and removed needs comments labels Dec 28, 2014
weaverryan added a commit that referenced this issue Dec 29, 2014
@weaverryan
feature #4173 use a global Composer installation (xabbuh)
55a32cf 
This PR was merged into the 2.3 branch.

Discussion
----------

use a global Composer installation

| Q             | A
| ------------- | ---
| Doc fix?      | yes
| New docs?     | no
| Applies to    | all
| Fixed tickets | #4170

This pull request replaces all mentions of local Composer installations, but uses a gobal Composer installation instead.

**Note:** This should be considered on hold and not be merged until we have an agreement on this in #4170.

Commits
-------

9ab1c56 use a global Composer installation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
DX hasPR A Pull Request has already been submitted for this issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0