unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@pragmatique.xyz>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: guix-devel@gnu.org
Subject: Re: font-build-system
Date: Thu, 11 May 2017 20:15:00 +0000	[thread overview]
Message-ID: <20170511201500.xopertmlrwg4pvue@abyayala> (raw)
In-Reply-To: <c637e04d.AEAAKEMQ_EEAAAAAAAAAAAOtZhgAAAACwQwAAAAAAAW9WABZFLzW@mailjet.com>

Arun Isaac transcribed 0.6K bytes:
> 
> ng0 writes:
> 
> > we have 20 - 25 fonts (I didn't really count), and only 2 are using a
> >
> > system* make args
> >
> > in their build phase, every other font just extracts, creates folders
> > and copies the fonts to the folders.
> > This is much repetition which could be avoided by just calling a build
> > system, rather than applying changes to fonts over and over again.
> >
> > It looks like this can be achieved by something as small as the emacs
> > build-system. Would anyone give it a try?
> 
> Is anybody working on this? I'd like to give this a shot, if nobody else
> is working on it already.
> 

I don't think anyone is working on a font-build-system. But this won't
solve the fc-cache problem as the reply by Mark suggests.

A build system would be good though.
-- 
https://pragmatique.xyz
PGP: https://people.pragmatique.xyz/ng0/

  reply	other threads:[~2017-05-11 20:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-05 12:58 font-build-system ng0
2017-02-13 14:59 ` font-build-system Ludovic Courtès
2017-05-11 19:34 ` font-build-system Arun Isaac
2017-05-11 20:15   ` ng0 [this message]
2017-05-11 22:19     ` font-build-system vs fc-cache profile hook Danny Milosavljevic
2017-05-13  5:10     ` font-build-system Arun Isaac
     [not found]     ` <cu7bmqx1gvl.fsf@systemreboot.net>
2017-05-15 16:35       ` font-build-system Arun Isaac

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170511201500.xopertmlrwg4pvue@abyayala \
    --to=ng0@pragmatique.xyz \
    --cc=arunisaac@systemreboot.net \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).