Hi Theo, On Tue, Oct 22, 2019 at 9:39 AM Theo Buehler <[email protected]> wrote:
> On Mon, Oct 14, 2019 at 11:34:32AM -0700, Peter Ezetta wrote: > > Hello ports@, > > > > Attached is a new Zola port, updated to v0.9.0. > > > > v0.9.0 Changelog: > > https://github.com/getzola/zola/blob/master/CHANGELOG.md#090-2019-09-28 > > > > I have removed the patches that I had in the 0.8.0 version, as they were > > merged upstream. the libc crate is bumped to support SPARC64, and the > > openssl-sys crate is bumped to support LibreSSL 3.0.1. > > Unfortunately, we're already at LibreSSL 3.0.2 in -current, so the build > fails with the usual panic in openssl-sys. A PR to support LibreSSL 3.0.x > was merged, but there's no release containing it at the moment: > > https://github.com/sfackler/rust-openssl/pull/1176 > > I think it's not a good idea to mention a specific LibreSSL version in > the Makefile, as it will be outdated rather quickly. > > Updated port attached -- comment removed. > How are going to cope with the failing build in -current that is bound > to happen once bcook@ bumps to LibreSSL 3.1.0 at some point during this > release cycle? > That is a great question. I have coping with the breakage so far by building the code regularly, and opening issues upstream when a new build of openssl-sys is required due to a LibreSSL release. I don't think this scales well, and don't have much of a desire to have the build break in -current every time there is a new LibreSSL release. Looking through the ports tree, it appears that both sysutils/exa and security/sn0int are both using openssl-sys, with v0.9.47 and v0.9.46, respectively. I don't see anything special in those ports to deal with LibreSSL -- neither of them are even updating openssl-sys during the build. I did notice, however, that they don't seem to be linking ssl, either, so perhaps that is why they're able to complete the build? Any advice on how to deal with this? Peter
zola.tar.gz
Description: application/gzip
