Compatibility with psr/container 1.1 about php-psr

[jbboehr]

Okay, I've opened #85 with psr/[email protected]

I also implemented 2.0 [0], but literally none of the libraries we test against are using it yet and it totally breaks them, so probably should hold off on that.

[stof]

@jbboehr the change done in a minor version was perfectly valid, thanks to variance rules.

The issue is that enabling this extension ignores entirely the package requirements (as the interface at the version selected by composer won't be loaded at all).
This extension basically defeats any attempt of versioning the PSR packages.

[sergeyklay]

Is this works for you:

{
    "require": {
        "ext-psr": "*"
    },
    "provide": {
        "psr/container": "^1"
    },
}

[derrabus]

@sergeyklay No, that would just uninstall the psr/container package.

[sergeyklay]

Well, as far as I know, this is usually what you should do anyway. Otherwise, you end up with two sources providing the same interface.

[jbboehr]

Kinda surprised they would change the interface in a non-major version. Looks like there's a 2.0 version out. I suppose we should update. Can you foresee any compatibility issues with phalcon @sergeyklay ?

[jbboehr]

Based on my reading of the mailing list at the time, it was my understanding that breaking interface changes would be published as a new library (e.g. psr/container2). It looks like they are not doing this.

[Jeckerson]

@jbboehr Could you create separate branch with updated interfraces so I could test it?

In case if this interfaces changes will break something from our side we will wait for new release from you. As we are almost ready to release Phalcon with PHP8 support: phalcon/cphalcon#15287

[jbboehr]

The issue is that enabling this extension ignores entirely the package requirements (as the interface at the version selected by composer won't be loaded at all).
This extension basically defeats any attempt of versioning the PSR packages.

This is just how extensions work and there is no resolution unless composer provides support for managing extensions. And well, I foolishly wasn't expecting there to ever be another version of a PSR without it being published as a new PSR in another namespace.