Date: Thu, 02 Feb 2017 16:25:15 +0100 From: Alexander Leidinger <Alexander@leidinger.net> To: Tijl Coosemans <tijl@freebsd.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r433087 - in head/x11-fonts: linux-c6-fontconfig linux-c7-fontconfig Message-ID: <20170202162515.Horde.0GFmTsPkuQPyWLWM5mZ_kSf@webmail.leidinger.net> In-Reply-To: <20170202135416.2d390f3a@kalimero.tijl.coosemans.org> References: <201702012010.v11KAfjg059841@repo.freebsd.org> <20170202100956.Horde.DPu6WjftKqJCtC5OCBpQf6o@webmail.leidinger.net> <20170202135416.2d390f3a@kalimero.tijl.coosemans.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This message is in MIME format and has been PGP signed. --=_bag3qisfWkIhLxAMCR3SgvE Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Tijl Coosemans <tijl@freebsd.org> (from Thu, 2 Feb 2017=20=20 13:54:21=20+0100): > On Thu, 02 Feb 2017 10:09:56 +0100 Alexander Leidinger=20=20 >=20<Alexander@leidinger.net> wrote: >> Could it be that a simple ln of the linux /var/db/fontconfig to the >> FreeBSD location would solve this issue without the need to run the >> linux fc-cache on each font directory change? > > The config files aren't fully compatible and the Linux fc-cache prints > some errors about that but they can be ignored it seems. > > The cache files have names ending in -<arch>.cache-<version> where <arch> > is le32d4 on i386 and le64 on amd64 and <version> is 7 on FreeBSD, 3 on > CentOS 6 and 4 on CentOS 7, so a simple link doesn't work. Argh. > The commit also doesn't fully solve the problem. The amd64 package only > generates le64 cache files so running an i386 Linux program may still > create cache files in the user home directory. This also happens when > users update their fonts because font ports don't run Linux fc-cache on > installation. > > The only real solution is to build our own Linux fontconfig package using > devel/linux-*-devtools. Instead of linux-devtools I would prefer this (ok, 6 years old, so=20=20 maybe=20a little bit outdated on the linux side of things, but the=20=20 principle=20still stands): http://www.leidinger.net/blog/2011/02/25/howto-creating-your-own-updated-li= nux-rpm-for-the-freebsd-linuxulator/ =3D use a real linux in a VM The reason for this is, that we should stay as close as possible to a=20=20 real=20linux when we build something, and we can't guarantee this via=20=20 linux-devtools. Bye, Alexander. --=20 http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_bag3qisfWkIhLxAMCR3SgvE Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iQIcBAABAgAGBQJYk09bAAoJEKrxQhqFIICEHF4QALIdtvHQsMeZt8x9269MPAkx xLZgIVzVIU6u8Tu7gxEFtPIKMRfX7zm+s+spNqRBH4TRtR8aJv2eh9b4Hny97qyz lkkddG4sCe6b8XV3FnIhnXoiLO034zfApPlGfd2QVSDDUEH+tMcwh8jmLzSXY5db YNv6SPNL4pCoa3chEXBNPFcR6BjeiOGB2FzyYA/+HU1cHdYHfsTywS9aqU2qYivV m5DEGcfBtUKnaFwQW1YSYeOl9Yk1DIvfFsDQVVR0qPyHJ6yqeTjRIrP3qlDdw3xs DG2scoYSM8bhhRwweQQips7cHxf2C/HUPK6ZXdkGVeO1HHxzzkFvDcWYd8kl8vme w2E0WivIhVLA6UZ1qmxgYpcmu/+IBz/lLsePbPAAD7u7EZUVbxDZ5Uq/NYijdzIV McnMiYwlhMwZMA2+xp/VK8mQhXhKxvQCaVSsUufQHEV7dYRam/VxcSjrnbwsFdwa u7+20PWfduSKWaQA2H+DQFJJkUkvTY102ScVDx+J8hERgefxNlesip2nRg1gTji9 SJ88oFdf3Az+Lc+fxntsABgBxO1iU0Y1Wz8oXyN2wzh9rKH0m03abvSUp5scbkgL hU3LKgPgdh5hiZoBSBJnB4HXQsnZl5Rulz68UTtGR2Hwjh7ipRLkVqsONEprrz+I o24C5sjw+38EWWSTdsIU =LBl9 -----END PGP SIGNATURE----- --=_bag3qisfWkIhLxAMCR3SgvE--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170202162515.Horde.0GFmTsPkuQPyWLWM5mZ_kSf>