Add support for configuring PEAR #34
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This should now work if the PEAR is already installed before the Vagrant run. I tried to hook into Vagrant's provisioner runs, but it doesn't seem to work. Have to take a closer look and ask help. |
[ci skip]
[ci skip]
tmatilai
added a commit
that referenced
this pull request
Jan 16, 2014
Add support for configuring PEAR
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It seems that PHP's extension manager PEAR doesn't support
http_proxyenv var, but has its own configuration command, which should be used for setting proxy configuration.Again we need to wait for hashicorp/vagrant#2405 so we can configure pear after it is installed in a provisioner run.