On Mon, Feb 17, 2020 at 04:27:23PM -0800, Peter Ezetta wrote:
> Hello ports@
> 
> Zola v0.10.0 was released recently. The changelog for this release is
> rather extensive, and can be viewed here:
> https://github.com/getzola/zola/releases/tag/v0.10.0
> 
> I struggled a little bit with rustls-native-certs during the update.
> Version 0.2.1 of this crate builds fine on OpenBSD, but I wound up chasing
> around dependency problems when I tried using the port module to update it
> from 0.1.0. Ultimately, I wound up patching rustls-native-certs to operate
> as if it were on a Linux machine on OpenBSD, as later versions of the crate
> have combined Linux with non-MacOS Unixes (including OpenBSD).
> 
> Is dropping the update of libc okay since the dependency has moved beyond
> the version that was required for SPARC64?

yes, it is fine to drop it now.
 
> Comments? Ok?

just a comment about openssl-sys patch

> Index: patches/patch-modcargo-crates_openssl-sys-0_9_54_build_main_rs
> ===================================================================
> RCS file: patches/patch-modcargo-crates_openssl-sys-0_9_54_build_main_rs
> diff -N patches/patch-modcargo-crates_openssl-sys-0_9_54_build_main_rs
> --- /dev/null 1 Jan 1970 00:00:00 -0000
> +++ patches/patch-modcargo-crates_openssl-sys-0_9_54_build_main_rs    17 Feb 
> 2020 23:45:30 -0000
> @@ -0,0 +1,14 @@
> +$OpenBSD$
> +
> +Index: modcargo-crates/openssl-sys-0.9.54/build/main.rs
> +--- modcargo-crates/openssl-sys-0.9.54/build/main.rs.orig
> ++++ modcargo-crates/openssl-sys-0.9.54/build/main.rs
> +@@ -204,7 +204,7 @@ See rust-openssl README for more information:
> +             (3, 0, 0) => ('3', '0', '0'),
> +             (3, 0, 1) => ('3', '0', '1'),
> +             (3, 0, _) => ('3', '0', 'x'),
> +-            _ => version_error(),
> ++            _ => ('3', '0', '0'),
> +         };

you should keep following the latest version by default. It is ('3', '0', 'x')
currently, and not ('3', '0', '0').

> + 
> +         println!("cargo:libressl=true");


-- 
Sebastien Marie

Reply via email to