public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: grace broken installation
Date: Tue, 28 Jan 2020 06:38:00 -0000	[thread overview]
Message-ID: <4082bff7-2778-102b-2c55-d8c3cbdafc78@SystematicSw.ab.ca> (raw)
In-Reply-To: <8d3ef7a0-5fee-29e4-6642-791f3491b812@t-online.de>

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

  reply	other threads:[~2020-01-28  6:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-25 14:24 Rodrigo Medina
2020-01-27  3:25 ` Hans-Bernhard Bröker
2020-01-27  5:32   ` Brian Inglis
2020-01-27 12:59   ` Ken Brown
2020-01-27 23:24     ` Hans-Bernhard Bröker
2020-01-28  6:38       ` Brian Inglis [this message]
2020-01-28 12:49         ` Ken Brown

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=4082bff7-2778-102b-2c55-d8c3cbdafc78@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    /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.
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).