Skip to content

Conversation

@rullzer
Copy link
Member

@rullzer rullzer commented Aug 30, 2016

No description provided.

@nickvergessen
Copy link
Member

The diff looks confusing, because the polyfill stuff actually didn't change, just the dependency of those?

@rullzer
Copy link
Member Author

rullzer commented Aug 30, 2016

Yes it seem so. It is just a version bump with some dep upgrades as I understand it.

@rullzer
Copy link
Member Author

rullzer commented Aug 30, 2016

Just want to get 3rdparty deps a bit more in shape again ;)

"require": {
"php": ">=5.3.3",
"paragonie/random_compat": "~1.0"
"paragonie/random_compat": "~1.0|~2.0"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is the dep of our dep, not a file we touch

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah. But using 2.0 here will break stuff. We can't take that. Sorry 👎

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also see the diff above, the 1.0 version has been replaced with 2.0. We should keep 1.0.x here for now.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Basically with 2.0 instances where /dev/urandom is not readable will fail pretty hard ;)

@nickvergessen
Copy link
Member

👍

@rullzer rullzer closed this Aug 31, 2016
@rullzer rullzer deleted the update_polyfill branch August 31, 2016 06:44
@nickvergessen
Copy link
Member

Since we drop the 5.4 and 5.5 support we can drop polyfill 5.5 snd 5.6?

@MorrisJobke
Copy link
Member

Since we drop the 5.4 and 5.5 support we can drop polyfill 5.5 snd 5.6?

See #11 ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants