Skip to content

Fix: Drop "replace" keys from composer.json#1291

Merged
glensc merged 11 commits intoeventum:masterfrom
glensc:drop-replace
Dec 12, 2021
Merged

Fix: Drop "replace" keys from composer.json#1291
glensc merged 11 commits intoeventum:masterfrom
glensc:drop-replace

Conversation

@glensc
Copy link
Copy Markdown
Member

@glensc glensc commented Dec 12, 2021

Using replace is nice way to minimize vendor size,
but it also makes it very difficult to install dependencies
when eventum/eventum is being used as "packages-dev"

The major obstacle is that "replace" may be provided by only one package
the way composer thinks.

The "replace" works fine when used as project, but we also want to use
eventum as library, for example extension development

NOTE: this removes "replace" key from committed version, but still uses it as release process.

@glensc glensc added this to the 3.10.10 milestone Dec 12, 2021
@glensc glensc self-assigned this Dec 12, 2021
@glensc glensc force-pushed the drop-replace branch 5 times, most recently from 53f392d to 04776af Compare December 12, 2021 20:32
glensc and others added 10 commits December 12, 2021 23:51
No sub-module is needed for building the release
Using replace is nice way to minimize vendor size,
but it also makes it very difficult to install dependencies
when eventun/eventum is being used as "packages-dev"

The major obstacle is that "replace" may be provided by only one package
the way composer thinks.

The "replace" works fine when used as project, but we also want to use
eventum as library, for example extension development
@glensc glensc marked this pull request as ready for review December 12, 2021 22:41
@glensc glensc merged commit 7e49c4f into eventum:master Dec 12, 2021
@glensc glensc deleted the drop-replace branch December 12, 2021 22:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant