Conversation
|
ps: i just noticed that pear-core-minimal is already in dev deps, but with a higher min version. I can amend this PR for that... |
sanmai
left a comment
There was a problem hiding this comment.
It will force everyone to install pear/pear-core-minimal even if they have pear/pear installed.
|
@sanmai you are right. This is why I think that, before merging this, some work needs to be done within the pear core packages, so that only one of either I have created an issue for that at pear/pear-core#142, but so far there has not been a lot of feedback... |
| ], | ||
| "require": { | ||
| "php": ">=5.6", | ||
| "pear/pear-core-minimal": "^1.0", |
There was a problem hiding this comment.
I think you'll need to remove the minimal entry in the dev section.
There was a problem hiding this comment.
I've made this update separately.
|
Are we sure |
|
Will test different scenarios, to determine what works best: whether specifying a minimum version of pear-core-minimal of 1.10.0 or 1.10.16 makes a difference, or whether that does not make any difference, but we still get double-installs when having pear/pear versions before 1.10.16)
|
|
@ashnazg I finally managed to do some testing. Sadly, the fix in pear/pear which went into rel. 1.0.16 has a typo, so atm if one is to depend on both I sent in a PR to fix that: pear/pear-core#153 Otoh, adding a dependency on both I thus propose the following plan:
|
|
I've applied your update in the context of including my review changes, and just released v1.0.1 for OLE after getting PEAR v1.10.17 out too. Closing this as handled... comment back if issue still seems to remain. |
I am not privy how PEAR is supposed to work when installed via Composer - whether packages such as this should depend on
pear-coreorpear-core-minimal, but still atm the OLE package does not work when installed stand-alone via composer