From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 35223 invoked by alias); 28 Jan 2020 06:38:15 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 35208 invoked by uid 89); 28 Jan 2020 06:38:15 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-8.3 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,GIT_PATCH_3,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 spammy=HX-Languages-Length:3117 X-HELO: smtp-out-so.shaw.ca Received: from smtp-out-so.shaw.ca (HELO smtp-out-so.shaw.ca) (64.59.136.139) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 28 Jan 2020 06:38:13 +0000 Received: from [192.168.1.114] ([24.64.172.44]) by shaw.ca with ESMTP id wKVmiDIKTRnrKwKVnifm2Z; Mon, 27 Jan 2020 23:38:11 -0700 Reply-To: Brian.Inglis@SystematicSw.ab.ca Subject: Re: grace broken installation To: cygwin@cygwin.com References: <08de4c07-3ec9-d169-bb56-b53b4367da12@cornell.edu> <8d3ef7a0-5fee-29e4-6642-791f3491b812@t-online.de> From: Brian Inglis Message-ID: <4082bff7-2778-102b-2c55-d8c3cbdafc78@SystematicSw.ab.ca> Date: Tue, 28 Jan 2020 06:38:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <8d3ef7a0-5fee-29e4-6642-791f3491b812@t-online.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2020-01/txt/msg00265.txt.bz2 On 2020-01-27 16:24, Hans-Bernhard Bröker wrote: > Am 27.01.2020 um 13:58 schrieb Ken Brown: >> On 1/26/2020 10:25 PM, Hans-Bernhard Bröker wrote: >>> Am 25.01.2020 um 15:23 schrieb Rodrigo Medina: >>>> Hi, >>>> Both   installations of grace-5.1.24 and grace-5.1.245 are  broken. >>>> /usr/bin/xmgrace.exe runs but gives the message: >>>> --> Broken or incomplete installation - read the FAQ! >>>> and then quits. > >>> After reading the FAQ and comparing with a direct build from upstream sources, I >>> find the reason for that is that the FontDataBase file of the distributed >>> package is, indeed, wrong. > >>> Apparently the type1 font directory supplied by grace was replaced by a link to >>> ghostscript's type1 font repository.  But the FontDataBase wasn't updated to >>> match this change.  This mismatch causes xmgrace to baulk.  This change was made >>> between revisions 5.1.24 and 5.1.25 of the cygwin package, which neatly explains >>> why 5.1.24 works, but 5.1.25 does not. >> >> See >> >> https://cygwin.com/ml/cygwin/2018-03/msg00142.html >> https://cygwin.com/ml/cygwin/2018-03/msg00156.html > > Yes, that's about what I figured.  The fonts supplied by xmgrace were replaced > (in the cygport file) by a link to ghostscript's fonts, but then those were > replaced by URW fonts, which broke xmgrace. > > OTOH the particular font files xmgrace is looking for are in yet another place > on Cygwin: > >     /usr/share/X11/fonts/urw-fonts > > And indeed, making the /usr/share/grace/fonts/type1 symlink point there > does appear to fix the breakage. > > So the minimal patch to grace.cygport (other than just leaving the type1 > directory of xmgrace alone) would be: > > $ diff -uwp grace.cygport{~,} > --- grace.cygport~      2017-06-27 09:43:32.000000000 +0200 > +++ grace.cygport       2020-01-28 00:08:56.345429500 +0100 > @@ -78,7 +78,7 @@ src_install() { >         rmdir doc >         ln -sf ../doc/${NAME} doc >         rm -fr fonts/type1 > -       ln -sf /usr/share/ghostscript/fonts fonts/type1 > +       ln -sf /usr/share/X11/fonts/urw-fonts fonts/type1 >         popd > >         make_desktop_entry xmgrace Grace xmgrace > "Education;Science;DataVisualization;Motif" > > An additional/changed dependency on the urw-base35-fonts-legacy package would > probably be needed, but I'll have to leave that to people who understand Cygwin > packaging. Links should only be applied during build processes to allow building and testing to complete successfully. Build link types may not be compatible with tar or the target file system and should not be included in packages for distribution e.g. they may only work on systems configured for WSL and with WSL installed. Distributed package links should be generated during post-install processing and should fall back to file copies if links are unsupported on the target file system. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple