Nothing is added to 16.04. That's the whole point of an LTS release.
-
-
... then, what's the point of your request? PHP 7.0 doesn't have native ext/sodium support, only 7.2 does.
1 reply 0 retweets 1 like -
Replying to @CiPHPerCoder @dzuelke and
If you can upgrade one, you can upgrade the other. Otherwise, there's no need to add backwards compat support for one in the other.
1 reply 0 retweets 0 likes -
Replying to @CiPHPerCoder @krakjoe and
If can not, and the standalone extension is for 7.0 and 7.1 as well.
2 replies 0 retweets 0 likes -
Replying to @dzuelke @CiPHPerCoder and
LTS distro + a couple hand-compiled things = frankenstein system that defeats the whole point.
2 replies 0 retweets 0 likes -
Replying to @jedisct1 @CiPHPerCoder and
Fellas. I simply put in a request to consider changing the requirement. I appreciate your feedback on how
@heroku keeps its systems running.1 reply 0 retweets 0 likes -
Replying to @dzuelke @CiPHPerCoder and
is run by human people that other people can talk to. Especially customers.
1 reply 0 retweets 0 likes -
Replying to @jedisct1 @CiPHPerCoder and
I'm not a customer. I work there. We will not switch from Ubuntu LTS to a fully hand built Linux.
2 replies 0 retweets 0 likes -
Replying to @dzuelke @CiPHPerCoder and
And you wouldn't be able to help build a backport / ppa that everybody could use and enjoy?
2 replies 0 retweets 0 likes -
Replying to @jedisct1 @CiPHPerCoder and
and I'm pretty certain we're not the only ones to run an LTS OS, with the specific intention of not having to wrestle sys lib updates
1 reply 0 retweets 0 likes
You can have hand compiled libs and system libs coexist. Set LD_LIBRARY_PATH before starting PHP.
-
-
Replying to @jedisct1 @CiPHPerCoder and
I know all these things. Of course I *could* build my own libsodium. That's not the point.
1 reply 0 retweets 0 likes -
What I don't understand is how you'd end up with PHP 7.2 and not also somehow get libsodium 1.0.13
4 replies 1 retweet 0 likes - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.