Skip to content
Snippets Groups Projects
Commit 8f168152 authored by homotechsual's avatar homotechsual
Browse files

Apply 1 suggestion(s) to 1 file(s)

parent 6e4399f9
No related branches found
No related tags found
No related merge requests found
......@@ -120,20 +120,6 @@ If you'd like more details to understand these commands or common errors, then p
pkgs and inhouse/private pkgs, and given how inhouse pkgs tend to have lax versioning, i can see how there'd
be pressure on D8 site-builders to make the configuration promiscuous -->
??? question "How to resolve conflicts in `pear/exception`?"
In some D8 configurations, you may see an error message about the package `pear/exception`. This is
because some packages use `pear/exception` -- but they have been overly specific about the required
version. (To wit: they require version `1.0.0` when version `1.0.1` will also work.)
To resolve this error, you can install v1.0.1 and *pretend* that it is v1.0.0:
```
composer require pear/pear_exception:'1.0.1 as 1.0.0'
```
After fixing this, you may continue the regular installation commands.
<!--
Optionally you can also require the [`cv`](https://github.com/civicrm/cv) command-line helper/interface for CiviCRM with:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment