Date: Sat, 1 Jan 2011 07:22:58 +1300 From: Thomas Zander <thomas.e.zander@googlemail.com> To: Eygene Ryabinkin <rea@freebsd.org> Cc: ports@freebsd.org, Michal Varga <varga.michal@gmail.com> Subject: Re: multimedia/mencoder - why do we build it without fontconfig support? Message-ID: <AANLkTimgQkFWnh2Y0VRDwq5NhARcOvp%2Bz=xAhFc0WBNY@mail.gmail.com> In-Reply-To: <zjaJq/aiWCHzGRHE0hjmTQByL0U@QsmfhJNucgI88DfvPJdT1/nyboE> References: <1293731589.5211.19.camel@xenon> <zjaJq/aiWCHzGRHE0hjmTQByL0U@QsmfhJNucgI88DfvPJdT1/nyboE>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, my main reason (as usual) for permanently disabling features from mplayer and mencoder is if something does not work reasonably well or almost nobody needs it. Supporting everything that they can do (more or less) via OPTIONS would just be a devilishly long list. With fontconfig and mencoder, the reason was to reduce the dependency list for those who run mencoder on a headless system, and it didn't seem to be a problem since I can't remember a discussion about it on the mailing list. Good that you posted that link, I don't follow this forum regularly. I think I could live with fontconfig being an OPTION for mencoder, as long as it's disabled by default. Would you guys prepare a suitable patch and get it committed, I am on vacation far away from my FreeBSD box at the moment. Thank you and happy new year Riggs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimgQkFWnh2Y0VRDwq5NhARcOvp%2Bz=xAhFc0WBNY>