From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Enge <andreas@enge.fr>
Subject: Re: Gs
Date: Sat, 23 Jul 2016 16:52:20 +0200
Message-ID: <20160723145220.GA7008@solar>
References: <20160722220501.GA6445@solar>
 <87twfgmxas.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:50667)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1bQyHz-0000Kl-Nf
	for guix-devel@gnu.org; Sat, 23 Jul 2016 10:52:28 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1bQyHw-0004Ui-B3
	for guix-devel@gnu.org; Sat, 23 Jul 2016 10:52:27 -0400
Received: from mailrelay7.public.one.com ([91.198.169.215]:22643)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1bQyHv-0004UW-UA
	for guix-devel@gnu.org; Sat, 23 Jul 2016 10:52:24 -0400
Content-Disposition: inline
In-Reply-To: <87twfgmxas.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Ludovic =?iso-8859-15?Q?Court=E8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org

Hello!

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.

Then after core-updates is merged, we could add the gs->gsc link to our
ghostscript packages.

What do you think?

Andreas