From owner-freebsd-ports@freebsd.org Sat Jan 13 01:02:13 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5AC67E6360E for ; Sat, 13 Jan 2018 01:02:13 +0000 (UTC) (envelope-from dan@langille.org) Received: from clavin2.langille.org (clavin2.langille.org [199.233.228.197]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "clavin.langille.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 302186957F; Sat, 13 Jan 2018 01:02:12 +0000 (UTC) (envelope-from dan@langille.org) Received: from (clavin2.int.langille.org (clavin2.int.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) with ESMTPSA id 7C6C31F28E ; Sat, 13 Jan 2018 01:02:10 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: www/rubygem-passenger creating slave ports From: Dan Langille X-Mailer: iPhone Mail (15C153) In-Reply-To: <20180113003346.GF9882@FreeBSD.org> Date: Fri, 12 Jan 2018 20:02:08 -0500 Cc: FreeBSD Ports Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180113003346.GF9882@FreeBSD.org> To: "Sergey A. Osokin" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Jan 2018 01:02:13 -0000 Hello Sergey, The proposed solution is a short term solution which goes away when FLAVORS a= re done for ruby. This is not soon.=20 We (feld@ & I) choose this solution as it has very little affect on the exis= ting port.=20 The need arose today & we hope to proceed quickly with whatever can be done.= =20 How do you suggest we proceed with the work? Thank you --=20 Dan Langille http://langille.org/ > On Jan 12, 2018, at 7:33 PM, Sergey A. Osokin wrote: >=20 > Hi Dan, >=20 > I don't see any reason to create two separate ports in this case and suppo= rt > them then cause potentially it's possible to modify the existing port to g= et > the same result. >=20 > --=20 > Sergey A. Osokin >=20 >> On Fri, Jan 12, 2018 at 10:18:37AM -0500, Dan Langille wrote: >> Sergey, >>=20 >> We have a need to use rubygem-passenger with both Nginx and with Apache (= on different servers). >>=20 >> I propose to create two new slave ports: >>=20 >> * www/rubygem-passenger-nginx >> * www/rubygem-passenger-passenger >>=20 >> To do this, I would like to make a one-line change to the master port: >>=20 >>=20 >> Index: Makefile >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- Makefile (revision 458852) >> +++ Makefile (working copy) >> @@ -24,7 +24,7 @@ >> APACHE22_DESC=3D Build with apache22 support >> NGINX_DESC=3D Build with nginx support >> SYMLINK_DESC=3D Create passenger symlink >> -OPTIONS_DEFAULT=3D APACHE22 >> +OPTIONS_DEFAULT=3D? APACHE22 >>=20 >> USE_RUBY=3D yes >> RAKE_BIN=3D ${LOCALBASE}/bin/rake >>=20 >> This will allow the slave port to set OPTIONS_DEFAULT and build for the d= esired web server. >>=20 >> If you agree, I am happen to make the commit / submit a patch for your ap= proval. >>=20 >> Thank you. >>=20 >> --=20 >> Dan Langille - BSDCan / PGCon >> dan@langille.org >>=20 >>=20