unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [PATCH] Hardcode “gs” path in Lilypond.
Date: Mon, 12 Oct 2015 20:43:44 +0200	[thread overview]
Message-ID: <87pp0k9bbz.fsf@gnu.org> (raw)
In-Reply-To: <87y4f8ziec.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 12 Oct 2015 08:54:19 +0200")

Ricardo Wurmus <rekado@elephly.net> skribis:

> the attached patch changes the result of ‘(search-gs)’ in the Lilypond
> backend, such that it returns the “gs” executable from the very same
> version of ghostscript that Lilypond was built with.
>
> Retaining a reference to ghostscript causes a closure increase from
> 309.9 to 351.2.  “gs” is required at runtime in order to compile
> Lilypond files to PDF (the default output format).  Without “gs” only
> the postscript file is generated and the compilation fails unless the
> output format is explicitly set to something other than PDF.

Makes sense.

> From c98b44ba82e45ebcb802bc1852128624f647b580 Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <rekado@elephly.net>
> Date: Sun, 11 Oct 2015 11:24:20 +0200
> Subject: [PATCH] gnu: lilypond: Hardcode path to "gs" executable.
>
> * gnu/packages/music.scm (lilypond)[arguments]: Add build phase
>   "hardcode-path-to-gs".

OK!

Ludo’.

      reply	other threads:[~2015-10-12 18:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12  6:54 [PATCH] Hardcode “gs” path in Lilypond Ricardo Wurmus
2015-10-12 18:43 ` Ludovic Courtès [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=87pp0k9bbz.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).