On Sun, Oct 27, 2019 at 04:18:56PM +0100, Sebastien Marie wrote: > On Wed, Oct 23, 2019 at 11:42:13AM -0700, Peter Ezetta wrote: > > Hi Theo, > > > > > 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? > > Hi, > > The following tarball should do the trick. It contains a patch on openssl-sys > to > use the latest available version in openssl-sys. I use this patch on cargo > (lang/rust port). > > I also changed the version to keep openssl-sys 0.10.24 instead of forcing > 0.10.25. I think it will work mostly the same way, as long the crates doesn't > use very recent stuff.
Thanks, this makes sense to me. ok tb to import > > Thanks. > -- > Sebastien Marie
