Timeline for What's the correct way to install Drupal with Composer if I want to work on core issues?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 19, 2020 at 13:24 | comment | added | mpdonadio♦ |
@joachim No, if I mess with composer.json or composer.lock, I just restore it to origin afterwards. If I don't, then the lockfile never changes. I have never found it to be a hassle. The core dependencies are mostly stable; they tend to change near a release if bumping the Symfony point releases change. I worked on at least five issues this weekend, and don't think I needed to worry about composer once.
|
|
| Feb 19, 2020 at 10:05 | comment | added | joachim | And then you're forever having to muck about with the composer.lock file when you want to make patches, aren't you? | |
| Feb 17, 2020 at 16:12 | comment | added | mpdonadio♦ |
@joachim Yeah, git clone, checkout the branch I want, then composer install. You want a git clone of the official repo so that the git indexes matches up when you have tricky applies/rerolls.
|
|
| Feb 17, 2020 at 10:51 | comment | added | joachim |
How do you install Drupal in the first place -- is it just a git clone that you then run composer install on?
|
|
| Feb 16, 2020 at 16:30 | history | answered | mpdonadio♦ | CC BY-SA 4.0 |