From owner-freebsd-ports@FreeBSD.ORG Wed May 8 12:49:53 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1DA41BB2; Wed, 8 May 2013 12:49:53 +0000 (UTC) (envelope-from feld@feld.me) Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) by mx1.freebsd.org (Postfix) with ESMTP id 3FA2CD26; Wed, 8 May 2013 12:49:50 +0000 (UTC) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 974D520E3; Wed, 8 May 2013 08:49:49 -0400 (EDT) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Wed, 08 May 2013 08:49:49 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=feld.me; h= content-type:to:subject:references:date:cc:mime-version :content-transfer-encoding:from:message-id:in-reply-to; s= mesmtp; bh=Zu0uwnNTAPMin3qLZUvpJE2BNFc=; b=CJzukdrgbcgIg48doTNa7 3B/c8sf1chKhn98fyVrOACScNoS93avDA1rg0fz5Ap1fhtfjvGxlDrQ5je4lrlYA JdBfWyIGd0ErtSm5K76Lqup4M1kWy6CWiKiMP/hTn07ExFEb2XuueQkMFPj6xbJz xkiq5/P16uLpHFN5+kGHrU= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:to:subject:references:date :cc:mime-version:content-transfer-encoding:from:message-id :in-reply-to; s=smtpout; bh=Zu0uwnNTAPMin3qLZUvpJE2BNFc=; b=gqys FvubfUlj+lTPSevARPxoJQFQiJ2ZAV9jIxbLgy94NeYDRohgbhDnA1J5P39QXP58 3ob2DaYIgfGNoTtC3p5UcnM03hYQqi/uQzpvaa3Yx0hlYYJqjgglx/2MuxwP2/o0 lauRUKbYZKwmw2rq0wgiKktsms0EISsn49HAW54= X-Sasl-enc: Myt4CbitvFFJZJlH8WMn7GyIFZc+/Pp5yzam3MTHurdM 1368017389 Received: from tech304.office.supranet.net (unknown [66.170.8.18]) by mail.messagingengine.com (Postfix) with ESMTPA id 2A3BFC8000E; Wed, 8 May 2013 08:49:49 -0400 (EDT) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "freebsd-ports@FreeBSD.org" Subject: Re: FreeBSD's PHP port incomplete; missing ftp_ssl_connect function References: <518A46EE.2060708@FreeBSD.org> Date: Wed, 08 May 2013 07:49:48 -0500 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Mark Felder" Message-ID: In-Reply-To: <518A46EE.2060708@FreeBSD.org> User-Agent: Opera Mail/12.14 (FreeBSD) Cc: "ale@freebsd.org" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 May 2013 12:49:53 -0000 On Wed, 08 May 2013 07:37:02 -0500, Alex Dupre wrote: > > Actually you can get a ssl-enabled php5-ftp in a very simple way: build > php5-ftp after php5-openssl. > Said so, such behavior should be harmonized, probably you could get a > ssl-enabled php5-ftp even without php5-openssl. I'll work on a patch. That makes total sense but I never experimented further after seeing the "official" PHP response saying you have to do it statically and seeing what other Linux distros were doing. However, this would still exclude cleanroom package building environments like poudriere or tinderbox, correct? We're deploying our software to our servers with pkgng packages and building with poudriere. I guess if you make php5-ftp have a build option for SSL that pulls in php5-openssl as a build dependency this might work, right? I really hope this is a simpler solution than I thought!