From owner-freebsd-ports@freebsd.org Thu Apr 28 15:27:00 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 82326B1FF4E for ; Thu, 28 Apr 2016 15:27:00 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [81.2.117.100]) (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 0C3C31E87 for ; Thu, 28 Apr 2016 15:26:59 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from ox-dell39.ox.adestra.com (unknown [85.199.232.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id C9BE5BC89 for ; Thu, 28 Apr 2016 15:26:49 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=FreeBSD.org Authentication-Results: smtp.infracaninophile.co.uk/C9BE5BC89; dkim=none; dkim-atps=neutral Subject: Re: Ports with X11 options To: freebsd-ports@freebsd.org References: <20160428144920.GJ71021@pcjas.obspm.fr> From: Matthew Seaman Message-ID: <78073ca2-829f-a54b-1654-4c0e2c363eab@freebsd.org> Date: Thu, 28 Apr 2016 16:26:49 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <20160428144920.GJ71021@pcjas.obspm.fr> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="F1IqcCOEA1AhNpH582NxRCTjTQlRjmWSI" X-Virus-Scanned: clamav-milter 0.99.1 at smtp.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-0.4 required=5.0 tests=BAYES_00,RDNS_NONE, SPF_SOFTFAIL autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on smtp.infracaninophile.co.uk X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2016 15:27:00 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --F1IqcCOEA1AhNpH582NxRCTjTQlRjmWSI Content-Type: multipart/mixed; boundary="8rkbdW0bxg0oSuW2ScbmNhlJit2cFDJt6" From: Matthew Seaman To: freebsd-ports@freebsd.org Message-ID: <78073ca2-829f-a54b-1654-4c0e2c363eab@freebsd.org> Subject: Re: Ports with X11 options References: <20160428144920.GJ71021@pcjas.obspm.fr> In-Reply-To: <20160428144920.GJ71021@pcjas.obspm.fr> --8rkbdW0bxg0oSuW2ScbmNhlJit2cFDJt6 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 04/28/16 15:49, Albert Shih wrote: > Some ports got a option =C2=AB WITH_X11 =C2=BB. I would like to > known what's that mean on a server ? Can I safely disable every WITH_X1= 1 if > those software is for a server. >=20 > For example, php-gd need graphics/cairo. If I disable X11 can I got som= e > issue with php-gd ? This depends very much on the port in question. Yes, for some ports WITH_X11 means the software is compiled so that it can make use of a graphical environment, and that is generally safe to turn off on a server= =2E For other ports, like GD, these use bits of X Windows to generate images -- typically something like using X fonts to render text into the image. In these cases, turning off the X11 support will remove that functionality, which may or may not be what you want. It's also the case that some ports higher in the dependency tree sometimes expect their dependencies to have X support, but that isn't enforced through the ports. so turning off X in a dependency can break the build of some other ports. In general, X support for an application will need only the X client libraries, and those are not huge. Unless you're in a very constrained environment or you're a perfectionist[*], just leaving the server ports with X enabled is not going to cause you any terrible problems. Cheers, Matthew [*] Like me. I build packages for server deployment without X support as far as possible, and luckily it's not mandatory for pretty much anything we want to deploy. Except for Java stuff: JVMs always link against the X client libraries. But it took a few rounds of trial and error and fiddling with options under poudriere to get things building to my liking. --8rkbdW0bxg0oSuW2ScbmNhlJit2cFDJt6-- --F1IqcCOEA1AhNpH582NxRCTjTQlRjmWSI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJXIiu5AAoJEABRPxDgqeTnDpEP/2Dr6zVVQilg1YOj+WP92hxj KbPWO38uOL0aj/NKbT9MvQLIYsiBFOfCNtB6CHt4UPC20Yj33VoKZZyVA+EaVM6x 505LveSs2o9wpPwAsWHWwKSuyFy31p4uqO4v1jIiw4ETDs+D/PVhxLEQDQdxGBqT E+y8HkNuxbANBvKcIC2L6qYxnb3B6ggrvlnutFrpEtCsNNZ9mFd36xujTn1+s2VL VNvwZIPYWpO/F4ozeiPuy5r+itQZ6nk4EuIFH8HuAAhUaw7RJct7dxHyyHUBy49J SBqCdRNKGGTvxPVye54J06D+5ZqvStiGRDB3R1rhyEFOb8Eur/5zja50oLbLRjWV uu1SPDIJxfR54XbGkpU+l13NoBHvye61h/jwVmqHw0r+oe3JMEg3Rh1cFmDTvDNX TGp3HJKDQLV9LBA7KqlHwWhNMMazvqegNX403AtpHZMA0gAPk0gUm10KAuAMucyt ekuIt4x+uz0uvLGIqxQa9Txu4WUYYcu98hjpvZeyhN0gBewMHuUvq0uYzKnwfNgh 3mAkgJ0DxOILCYwqta3/BoRcZ+FlCePHfSkou2mbFXYYwxTs2CaXf0M6bjkvmMdO 8P0EkWuqRORo4c7g1Z1PwxoQTofdKZilHqKczeoNJ6qA9sEFJEOFlQCwJ3iynZww 3Ye5fChIScA2TXFqfhsk =WqRT -----END PGP SIGNATURE----- --F1IqcCOEA1AhNpH582NxRCTjTQlRjmWSI--