Date: Thu, 5 Dec 2013 12:45:34 +0100 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Muhammad Moinur Rahman <5u623l20@gmail.com> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: Force Dependent ports OPTIONS Message-ID: <20131205114534.GG76976@ithaqua.etoilebsd.net> In-Reply-To: <CA%2BnPUkw3zqCDRiKf1LbZsV6g4oxdNGWoe79CBKXqAgVn16QB_Q@mail.gmail.com> References: <CA%2BnPUkw3zqCDRiKf1LbZsV6g4oxdNGWoe79CBKXqAgVn16QB_Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Wtrm9ATX0sn6fFKv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 05, 2013 at 05:42:15PM +0600, Muhammad Moinur Rahman wrote: > Hi, >=20 > Let us suppose I am porting an application which depends on Openssl. But > not only OpenSSL, OpenSSL has to have some options enabled which are not > enabled by default. How can I force changing the knob? >=20 > Slave port is an option I have thought. But anything else? Thanks in > advance. >=20 Creating a slave port will be a nightmare for openssl, what option are you depending on? is it intrusive, does it make sense to have it by default? Those are the questions, depending on answers the good way could be to remo= ve the option from the openssl port and activate by default the feature. regards, Bapt --Wtrm9ATX0sn6fFKv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlKgZ14ACgkQ8kTtMUmk6Ex6owCeO8ttaIOowLQe0QP/+CVI2MqD qewAn25OvaUl1Y3DYqw2xRwPNIxLDnEY =SBKv -----END PGP SIGNATURE----- --Wtrm9ATX0sn6fFKv--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131205114534.GG76976>