Date: Thu, 30 Dec 2010 21:37:38 +0300 From: Eygene Ryabinkin <rea@freebsd.org> To: Michal Varga <varga.michal@gmail.com> Cc: ports@freebsd.org, riggs@rrr.de Subject: Re: multimedia/mencoder - why do we build it without fontconfig support? Message-ID: <zjaJq/aiWCHzGRHE0hjmTQByL0U@QsmfhJNucgI88DfvPJdT1/nyboE> In-Reply-To: <1293731589.5211.19.camel@xenon> References: <1293731589.5211.19.camel@xenon>
next in thread | previous in thread | raw e-mail | index | archive | help
--EDT6MSV0B3GxyNyZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Thu, Dec 30, 2010 at 06:53:09PM +0100, Michal Varga wrote: > So the question stands - is there anything to gain by having fontconfig > support forcefully disabled? After all this is mencoder we're talking > about, one dependency more or less is just a drop in the ocean. And the > current state really makes our mencoder kind of crippled... That's an almost obvious statement, but we can introduce an OPTION for the fontconfig support. What to have as the default, ON or OFF, is the question about why currently fontconfig is disabled. --=20 Eygene Ryabinkin ,,,^..^,,, [ Life's unfair - but root password helps! | codelabs.ru ] [ 82FE 06BC D497 C0DE 49EC 4FF0 16AF 9EAE 8152 ECFB | freebsd.org ] --EDT6MSV0B3GxyNyZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iF4EAREIAAYFAk0c0XIACgkQFq+eroFS7PsuHQD/dPACETFBt2WxeYO+qc98LiyW XTRXlUoNhkbFkQnM2EgA/2tYSVXGaVEwuHddx4w0tdR3N4YobMUwX2YK0wEc8Gjd =0NJr -----END PGP SIGNATURE----- --EDT6MSV0B3GxyNyZ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?zjaJq/aiWCHzGRHE0hjmTQByL0U>