Re: pkg/39433

[Taylor R Campbell <campbell%mumble.net@localhost>]

The following reply was made to PR pkg/39433; it has been noted by GNATS.

From: Taylor R Campbell <campbell%mumble.net@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: pkg-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, 
pkgsrc-bugs%netbsd.org@localhost
Subject: Re: pkg/39433
Date: Tue, 2 Sep 2008 17:27:14 -0400

    Date: Tue,  2 Sep 2008 14:15:04 +0000 (UTC)
    From: "Jeremy C. Reed" <reed%reedmedia.net@localhost>
 
    Does this work for you?
 
 I don't believe it will -- see below.
 
    Should it be openssl-zlib option like you suggested or just zlib?
 
 There is currently no `zlib' or `openssl-zlib' option in
 mk/defaults/options.description.  There is a `links-zlib' option,
 which is obviously inapplicable.  Adding a general `zlib' option, or
 enabling zlib by default (wherever it can be enabled), seems most
 sensible to me, but adding an `openssl-zlib' option would be least
 invasive.
 
    @@ -48,6 +48,13 @@
     CONFIGURE_ARGS+=   no-rc5
     .endif
 
    +.if !empty(PKG_OPTIONS:Mzlib)
    +CONFIGURE_ARGS+=   enable-zlib
    +.include "../../devel/zlib/buildlink3.mk"
    +.else
    +CONFIGURE_ARGS+=   no-zlib
    +.endif
    +
     .if !empty(OPENSSL_LICENSE)
     # pkgsrc does not handle multiple licenses
     LICENSE=   openssl-patented-algorithms-nonlicense
 
 The argument you have to pass to the configure script is `zlib', not
 `enable-zlib'.  There is another option, `zlib-dynamic', for using a
 zlib shared library if one is available, and proceeding without zlib
 if one is not available.  Considering the ubiquity of zlib, however, I
 think that using the vanilla `zlib' option is preferable.