This repository has been archived by the owner on Nov 9, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 60
Is PEAR supposed to be required? #78
Comments
This should not be an issue once #74 hits the master branch (should be next week when I plan to go through some due pull requests and issues). |
0.5.4 still requires PEAR.
|
Is it fixed? I got a same warning in 0.5.4.
|
Not that I'm saying console_commandline is inferior but I think it would be pretty neat to see a PR come in replacing it with Symfony/Console. Even though I haven't created a static site since about oh 8 months ago. |
It was temporary fixed on #101. If anybody wants get rid all PEAR stuff, you are welcome :-) |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Following the websites "Installation" page, I was getting an exception when trying to run phr relating to a file not being found. I figured out that when I installed PEAR (sudo apt-get install php-pear) it would then work. Aren't the PEAR dependencies supposed to be included in the phrozn package? If PEAR is a dependency, it should be included on the installation page.
The text was updated successfully, but these errors were encountered: