From owner-freebsd-ports@freebsd.org Mon Sep 19 11:19:16 2016 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 4DFF3BDF757 for ; Mon, 19 Sep 2016 11:19:16 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.shmhost.net (host64.kissl.de [213.239.241.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 16C29884; Mon, 19 Sep 2016 11:19:15 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from francos-mbp.homeoffice.local (ipservice-092-208-160-166.092.208.pools.vodafone-ip.de [92.208.160.166]) by host64.shmhost.net (Postfix) with ESMTPSA id E4E6B80D89; Mon, 19 Sep 2016 13:19:11 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: Checking port option descriptions From: Franco Fichtner In-Reply-To: <57DFC4FE.2080303@quip.cz> Date: Mon, 19 Sep 2016 13:19:11 +0200 Cc: Matthew Seaman , freebsd-ports@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <9E3B72C9-AA6A-46C4-A421-BFD125295C23@lastsummer.de> References: <57DF9841.7000500@quip.cz> <2d4f9827-fa51-3950-0bcf-76d54143dd21@freebsd.org> <57DFC4FE.2080303@quip.cz> To: Miroslav Lachman <000.fbsd@quip.cz> X-Mailer: Apple Mail (2.3124) X-Virus-Scanned: clamav-milter 0.99.2 at host64.shmhost.net X-Virus-Status: Clean X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2016 11:19:16 -0000 > On 19 Sep 2016, at 12:59 PM, Miroslav Lachman <000.fbsd@quip.cz> = wrote: >=20 > In the end of this story - we are no longer using ports versions for = any PHP web applications. We are using them directly because ports were = more problematic. We use various PHP packages from ports for a larger project without any issues or having to deal with custom options. It has also gotten a lot better in the last two years from a ports framework perspective. Yes, some things get messy when you go against the framework, but that only leaves the option to make the framework more flexible or deal with the custom build by building another framework. If there is an incompatibility between the two approaches I don't see how e.g. your issues will be resolved by changing the ports framework. If there aren't any incompatibilities it's just work to get it done. :) > pkg is too interactive anyway (compared to any older method) so I = don't think this will be a problem. I think it will be useful to do this = on install phase instead of package building phase. pkg scripts really well compared to e.g. OpenBSD's pkg_add, which at least for 5.9 cannot non-interactively select ambiguous flavors. You can see the latter was designed and nurtured from a user's point of view, but deploying jails or custom images with packages is way easier with FreeBSD's pkg. It's not perfect either, but it's in better shape than you might believe. Cheers, Franco=