You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 11, 2019. It is now read-only.
Afaik the composer library/module is for php what pip is for python? If it is there is just one problem: composer keeps binaries on an exclusive bin folder.
So i kinda think: maybe my problem is to get a virtualenv for composer itself and not php at all, because the bin from composer are not linked over the bin folder from the virtphp which is the "goal" (for me) to use env.
I think it could be a nice catch to set the VIRTPHP_ENV_PATH with the composer/bin path on the activate file.
i've tried to manipulate the (environment variables)[https://getcomposer.org/doc/03-cli.md#composer-bin-dir] but notthing changed at the installation level. the only progress was to set the VIRTPHP_ENV_PATH to cover the original vendo folder.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Afaik the composer library/module is for php what pip is for python? If it is there is just one problem: composer keeps binaries on an exclusive bin folder.
So i kinda think: maybe my problem is to get a virtualenv for composer itself and not php at all, because the bin from composer are not linked over the bin folder from the virtphp which is the "goal" (for me) to use env.
I think it could be a nice catch to set the VIRTPHP_ENV_PATH with the composer/bin path on the activate file.
i've tried to manipulate the (environment variables)[https://getcomposer.org/doc/03-cli.md#composer-bin-dir] but notthing changed at the installation level. the only progress was to set the VIRTPHP_ENV_PATH to cover the original vendo folder.
The text was updated successfully, but these errors were encountered: