From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Gs
Date: Sat, 23 Jul 2016 13:03:07 +0200 [thread overview]
Message-ID: <87twfgmxas.fsf@gnu.org> (raw)
In-Reply-To: <20160722220501.GA6445@solar> (Andreas Enge's message of "Sat, 23 Jul 2016 00:05:01 +0200")
Hi!
Andreas Enge <andreas@enge.fr> skribis:
> the following commit
> commit eb354bdacbf4154ec66038dac07f19bf4ced1fad
> Author: Ludovic Courtès <ludo@gnu.org>
> Date: Mon May 9 15:54:34 2016 +0200
>
> gnu: ghostscript: Do not build the statically-linked 'gs' binary.
>
> * gnu/packages/ghostscript.scm (ghostscript)[arguments]: Remove
> 'build-so' and 'install-so' phases. Replace 'build' and 'install'
> phases.
Ahem, I plaid guilty.
> removes "gs" from the ghostscript package. However, this is the usual program
> that people expect. For instance, unison uses it for building its
> documentation. Is there a dynamically linked binary which replaces gs?
> If yes, should we add a symbolic link?
I think so.
For the current solution (avoiding a full rebuild), see commit
61dc82d9b90d0545739c30bfc33003bd062071f0. LilyPond could hard-code the
file name of ‘gsc’.
Alternately, we could provide a wrapper containing a ‘gs’ symlink.
This has been discussed with Efraim IIRC, though I can’t find the thread
now.
Thoughts?
Ludo’.
next prev parent reply other threads:[~2016-07-23 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 22:05 Gs Andreas Enge
2016-07-22 23:01 ` Gs Ricardo Wurmus
2016-07-23 11:03 ` Ludovic Courtès [this message]
2016-07-23 14:52 ` Gs Andreas Enge
2016-07-25 9:43 ` Gs Ludovic Courtès
2016-07-24 6:43 ` Gs Efraim Flashner
-- strict thread matches above, loose matches on Subject: below --
2016-07-23 11:09 Gs Federico Beffa
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=87twfgmxas.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--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).