mirror of
https://github.com/ostreedev/ostree.git
synced 2024-10-27 10:25:07 +03:00
361aa449fb
For rpm-ostree, we already link to libcurl indirectly via librepo, and only having one HTTP library in process makes sense. Further, libcurl is (I think) more popular in the embedded space. It also supports HTTP/2.0 today, which is a *very* nice to have for OSTree. This seems to be working fairly well for me in my local testing, but it's obviously brand new nontrivial code, so it's going to need some soak time. The ugliest part of this is having to vendor in the soup-url code. With Oxidation we could follow the path of Firefox and use the [Servo URL parser](https://github.com/servo/rust-url). Having to redo cookie parsing also sucked, and that would also be a good oxidation target. But that's for the future. Closes: #641 Approved by: jlebon
18 lines
623 B
YAML
18 lines
623 B
YAML
language: c
|
|
dist: trusty
|
|
sudo: required
|
|
|
|
env:
|
|
- ci_distro=ubuntu ci_suite=trusty ci_test=no # TODO: use libcurl on this
|
|
- ci_docker=debian:jessie-slim ci_distro=debian ci_suite=jessie
|
|
- ci_docker=debian:jessie-slim ci_distro=debian ci_suite=jessie ci_configopts="--with-curl"
|
|
- ci_docker=debian:stretch-slim ci_distro=debian ci_suite=stretch ci_test=no # TODO gpgme flake https://github.com/ostreedev/ostree/pull/664#issuecomment-276033383
|
|
- ci_docker=ubuntu:xenial ci_distro=ubuntu ci_suite=xenial
|
|
|
|
script:
|
|
- tests/ci-install.sh
|
|
- ci_parallel=2 ci_sudo=yes tests/ci-build.sh
|
|
|
|
notifications:
|
|
email: false
|