From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Gs
Date: Mon, 25 Jul 2016 11:43:04 +0200 [thread overview]
Message-ID: <87y44qoxxz.fsf@gnu.org> (raw)
In-Reply-To: <20160723145220.GA7008@solar> (Andreas Enge's message of "Sat, 23 Jul 2016 16:52:20 +0200")
¡Hola!
Andreas Enge <andreas@enge.fr> skribis:
> On Sat, Jul 23, 2016 at 01:03:07PM +0200, Ludovic Courtès wrote:
>> For the current solution (avoiding a full rebuild), see commit
>> 61dc82d9b90d0545739c30bfc33003bd062071f0. LilyPond could hard-code the
>> file name of ‘gsc’.
>
> This looks like too much work to implement for each package separately.
> And as a permanent solution, I do not like it.
>
>> Alternately, we could provide a wrapper containing a ‘gs’ symlink.
>
> This would be one option. Or we could add another package, corresponding
> to the previous definition, that we would use only as an input to the
> packages in core-updates that do not build right now. This solution could
> be implemented using copy-paste and not take much time. I would then also
> remove the ad-hoc lilypond patching.
I went ahead and pushed these two commits, which seem to address the
issue:
d8eb912 * gnu: Use 'ghostscript-gs' in packages that need the 'gs' command.
71eba3e * gnu: Add 'ghostscript-gs' and 'ghostscript-gs-with-x'.
> Then after core-updates is merged, we could add the gs->gsc link to our
> ghostscript packages.
Yes, we should do that afterwards.
Apologies for the breakage!
Ludo'.
next prev parent reply other threads:[~2016-07-25 9:43 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 ` Gs Ludovic Courtès
2016-07-23 14:52 ` Gs Andreas Enge
2016-07-25 9:43 ` Ludovic Courtès [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y44qoxxz.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.