From debbugs-submit-bounces@debbugs.gnu.org Thu May 11 15:48:11 2017 Received: (at 26877) by debbugs.gnu.org; 11 May 2017 19:48:11 +0000 Received: from localhost ([127.0.0.1]:39107 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d8u4J-00058W-8j for submit@debbugs.gnu.org; Thu, 11 May 2017 15:48:11 -0400 Received: from 93-95-228-241.1984.is ([93.95.228.241]:41476 helo=sharknado9001.pragmatique.xyz) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d8u4F-00058J-LL for 26877@debbugs.gnu.org; Thu, 11 May 2017 15:48:09 -0400 Received: by sharknado9001.pragmatique.xyz (OpenSMTPD) with ESMTPSA id 96fab2f7 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Thu, 11 May 2017 19:47:54 +0000 (UTC) Date: Thu, 11 May 2017 19:47:58 +0000 From: ng0 To: Mark H Weaver Subject: Re: bug#26877: building fonts: fontcache must be updated regulary Message-ID: <20170511194758.etpgtrboftdmptp4@abyayala> Mail-Followup-To: Mark H Weaver , 26877@debbugs.gnu.org References: <20170511083658.fuc54qhzo7ismnha@abyayala> <8760h7guba.fsf@netris.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <8760h7guba.fsf@netris.org> X-Spam-Score: 0.4 (/) X-Debbugs-Envelope-To: 26877 Cc: 26877@debbugs.gnu.org, ng0 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: debbugs-submit-bounces@debbugs.gnu.org Sender: "Debbugs-submit" X-Spam-Score: 0.4 (/) Mark H Weaver transcribed 1.2K bytes: > ng0 writes: > > > The problem: Right now after just installing fonts, they do > > not become available. This can lead to some applications > > appearing "broken", etc. Other operating systems solve this > > by having a post-install hook which roughly does just this. > > > > A possible solution: > > Our fictional, not yet existing, font-build-system should > > run "fc-cache --force --really-force", > > This cannot work, because the build system code is run within the build > container, where it won't have access to anything in your home > directory. Furthermore, for most users, the packages are built on > another machine, namely one of our build farm slaves. > > Even the build system did somehow have access to your home directory, > building the package is not the right time to run "fc-cache". On a > multiuser system, if two users request the same derivation, it is only > built for the first user, and the second user simply uses the one that > the first user built. The relevant time to run "fc-cache" is when the > font is _installed_ in your user profile. > > The usual Guix way to handle things like this is to arrange for the font > cache to be part of the profile, and to create a profile hook that > creates the cache from all of the built packages included within. > > Mark > Okay, you are right about the build system. Your approach reads better, I was just looking for a way to start a discussion on this. Right now it is not-obviously broken, and we need to fix it at some point. -- https://pragmatique.xyz PGP: https://people.pragmatique.xyz/ng0/