Skip to content
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.

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

Global composer config #133

Open
andig opened this issue Sep 9, 2017 · 3 comments
Open

Global composer config #133

andig opened this issue Sep 9, 2017 · 3 comments

Comments

@andig
Copy link

andig commented Sep 9, 2017

At least on OSX it should be

export PATH="$PATH:$HOME/.composer/vendor/bin"

not

export PATH="$PATH:$HOME/.config/composer/vendor/bin"

Not sure if the .config is working on other *nix versions?

@sstalle
Copy link
Owner

sstalle commented Sep 9, 2017

I changed it from $HOME/.composer to $HOME/.config/composer some time ago (see #103 ). I think the latter is used by default on new Ubuntu versions. Some of the other possible options are decribed in the Composer documentation, to which there is a link from README.md.

I'm not sure what can be done to make the fact this directory is OS-dependent more explicit. Listing the available options by copying and pasting part of the Composer documentation doesn't seem like a good idea to me. Do you have any suggestions on how to make it work better?

@andig
Copy link
Author

andig commented Sep 9, 2017

Do you have any suggestions on how to make it work better?

Not really as I don't have exposure to a broad level of distros. Only adding both pathes could make it copy/paste?

It just seems that the general statement of #103 is wrong. Its only a minor thing though.

@sstalle
Copy link
Owner

sstalle commented Sep 11, 2017

It just seems that the general statement of #103 is wrong.

It definitely does not apply to every OS/distro out there. I just thought that adding $HOME/.config/composer/vendor/bin and a link to the Composer doc that lists other possible alternatives would be enough. But maybe you are right and I should add all the cases that we are currently aware of to the installation guide. That would probably make a better user experience. It just feels somewhat wrong to repeat the things that are already explained pretty good elsewhere.

Thanks for bringing it up anyway, I'll think about ways of making the install guide more clear.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants