unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: L  p R n  d n    <guix@lprndn.info>
To: Brendan Tildesley <mail@brendan.scot>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Should font-build-system compile sfd fonts?
Date: Fri, 03 May 2019 17:23:51 +0200	[thread overview]
Message-ID: <87k1f78su0.fsf@lprndn.info> (raw)
In-Reply-To: <425a9e54-ed64-fa48-cf9c-f503439af3e7@brendan.scot> (Brendan Tildesley's message of "Fri, 3 May 2019 17:40:48 +1000")

Hello,

Brendan Tildesley <mail@brendan.scot> writes:

> I'm calling for anyone's opinion on this. Currently there are a few
> fonts which more-or-less copy-paste the same code for compiling sfd
> files in to ttf and otf, which requires fontforge. I wish to add another
> font, but didn't want to add to this duplication. Most fonts don't
> require it, but it wouldn't be harmful, apart from dragging in
> fontforge, would adding a 'build phase that does this to
> font-build-system be reasonable. I'm not actually sure how to add a
> required native-input to a build system. Or is there a better idea?
> Making a whole new sfd-font-build-system, or defining a build-sdf-fonts
> symbol that could be added with modify-phases and adding fontforge to
> native-inputs?

Maybe adding an optional phase like #:glib-or-gtk? for meson?
We would get a #sfd-font? argument in the font-build-system.

What do you think?

      reply	other threads:[~2019-05-03 13:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-03  7:40 Should font-build-system compile sfd fonts? Brendan Tildesley
2019-05-03 15:23 ` L p R n d n [this message]

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=87k1f78su0.fsf@lprndn.info \
    --to=guix@lprndn.info \
    --cc=guix-devel@gnu.org \
    --cc=mail@brendan.scot \
    /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).