Date: Mon, 14 Sep 2015 07:50:34 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Hiroki Sato <hrs@FreeBSD.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r396872 - in head: Keywords Mk/Uses Message-ID: <20150914055033.GA54344@ivaldir.etoilebsd.net> In-Reply-To: <201509132330.t8DNUMEd025676@repo.freebsd.org> References: <201509132330.t8DNUMEd025676@repo.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 13, 2015 at 11:30:22PM +0000, Hiroki Sato wrote: > Author: hrs > Date: Sun Sep 13 23:30:21 2015 > New Revision: 396872 > URL: https://svnweb.freebsd.org/changeset/ports/396872 >=20 > Log: > Add "fc", "fcfontsdir", "fontsdir", and "none" arguments to USES=3Dfont= s. > They controls whether fc-cache and/or mkfontdir run in > post-{,de}install targets. > =20 > japanese/font-* use manually generates fonts.dir entries to utilize > special modifiers which are useful for CJK fonts. Because mkfontdir > does not understand and silently remove them from fonts.dir, > options like fonts:fc or fonts:none is required. > =20 > Approved by: portmgr (bapt) Thank you! can you add a comment at the top of fonts.mk to explain this iss= ue? That would avoid someone else coming in a few years making the same mistake= as I did. Do you know how they do fix in linux land? because when working on the font= s, I found nothing special being done on any Linux distro, have I missed somethi= ng? Best regards, Bapt --KsGdsel6WgEHnImy Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlX2YCkACgkQ8kTtMUmk6ExLvwCfa6SmXnYYcnrUhp2/V+bvtvvc Wp0An2qsCI1NCMZXh0Mc8AXPSglHenNG =KaNx -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150914055033.GA54344>