Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
I
Installation Guide
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Monitor
Service Desk
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Documentation
Docs
Installation Guide
Commits
05cfae4f
Commit
05cfae4f
authored
3 years ago
by
homotechsual
Browse files
Options
Downloads
Patches
Plain Diff
Apply 1 suggestion(s) to 1 file(s)
parent
73bb3155
No related branches found
Branches containing commit
No related tags found
1 merge request
!37
Draft: Update Drupal 8/9 composer installation instructions
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/drupal9/index.md
+0
-15
0 additions, 15 deletions
docs/drupal9/index.md
with
0 additions
and
15 deletions
docs/drupal9/index.md
+
0
−
15
View file @
05cfae4f
...
@@ -127,21 +127,6 @@ If you'd like more details to understand these commands or common errors, then p
...
@@ -127,21 +127,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
pkgs and inhouse/private pkgs, and given how inhouse pkgs tend to have lax versioning, i can see how there'd
be pressure on D9 site-builders to make the configuration promiscuous -->
be pressure on D9 site-builders to make the configuration promiscuous -->
??? question "How to resolve conflicts in
`pear/exception`
?"
<!-- Is this still needed in D9? I feel like they fixed in later D8.x templates. -->
In some 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.
<!--
<!--
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment