3 ms·
Meanwhile, the Linux nightly build has been broken on all major distros for a while (see https://github.com/servo/servo/issues/12015 https://github.com/servo/se
by Aissen 10y ago
Meanwhile, the Linux nightly build has been broken on all major distros for a while (see https://github.com/servo/servo/issues/12015 https://github.com/servo/servo/issues/12015 ), because the project won't bundle openssl. For a nightly. Which they already do for Firefox (all release channels). And of course, there are bundling it for this Windows nightly as well…
- Aissen 10y agoAnd I just checked, it's the same on MacOS, where libssl is bundled. I guess they've made their mind on the priorities.
- larsberg 10y agoThe awesome avadacatavra is working on a plan right now to move us off of OpenSSL: https://github.com/servo/servo/issues/7888#issuecomment-293405504 https://github.com/servo/servo/issues/7888#issuecomment-2934... TBH, it's been hard to prioritize work to fix OpenSSL issues when we all knew it was going away from the dependency list. However, I don't think anybody anticipated the scope of work required to get there :-) Sorry for the inconvenience!
- Aissen 10y agoI understand, but then why bundle it for MacOS & Windows, and not Linux ? Couldn't they, too, wait for OpenSSL to go away ? Note that I fully support using a clean rust-based TLS implementation. Given how young servo is, it will have time to mature before Servo becomes widely-deployed. I just think this is an orthogonal problem. PS: thanks for taking the time to answer here and keep up the good work !