From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: gnuplot-5.4.0-1
Date: Sat, 18 Jul 2020 13:37:28 -0600 [thread overview]
Message-ID: <4ace67ed-914f-3107-7f4f-74b11c83c056@SystematicSw.ab.ca> (raw)
In-Reply-To: <fa38e246-80d0-5740-c52b-0ee1a4a43f66@SystematicSw.ab.ca>
On 2020-07-18 11:45, Brian Inglis wrote:
> On 2020-07-18 10:45, Thomas Wolff wrote:
>> Am 18.07.2020 um 18:40 schrieb Thomas Wolff:
>>> Am 18.07.2020 um 18:31 schrieb Thomas Wolff:
>>>> Am 18.07.2020 um 09:55 schrieb Achim Gratz:
>>>>> Gnuplot version 5.4.0 is now available on Cygwin. The upstream release
>>>>> notes are available at:
>>>>> http://www.gnuplot.info/ReleaseNotes_5_4.html
>>>>> Cygwin Notes
>>>>> Depending on which packages you install running plain
>>>>> "gnuplot" will dispatch different executables via the alternatives
>>>>> system.
>>>> running setup, gnuplot-base is updated from 5.4 rc2 to 5.4, but package
>>>> gnuplot has vanished.
>>> Errh, which you explained above, sorry. Anyhow, gnuplot.exe did not get
>>> installed.
>> OK, it's called gnuplot-base now. Is it a good idea to drop plain gnuplot as an
>> invocation name?
> Release notes suggest there should be a file /var/lib/alternatives/gnuplot to
> define a symlink /bin/gnuplot to /etc/alternatives/gnuplot and that symlinks to
> /bin/gnuplot-base.
>
> Please check if /etc/postinstall/gnuplot.sh.done exists and completed
> successfully in /var/log/setup.log.full or /var/log/setup.log and the
> alternatives were created successfully, as above.
Script to setup postinstall alternatives is actually called gnuplot-base.dash
and the executable name does not look as if alternatives will use it:
$ tar -x -O \
-f mirror/x86_64/release/gnuplot/gnuplot-base/gnuplot-base-5.4.rc2-0.tar.xz \
etc/postinstall/gnuplot-base.dash
/usr/sbin/alternatives --install /usr/bin/gnuplot gnuplot
/usr/bin/gnuplot-{BB}.exe 10
AFAIK alternatives is not going to do anything special with gnuplot-*{BB}*.exe:
perhaps intended to be generated with "*$*{BB}" == "base" but missing *$*?
--
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.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-07-18 19:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 7:55 Achim Gratz
2020-07-18 16:31 ` Thomas Wolff
2020-07-18 16:40 ` Thomas Wolff
2020-07-18 16:45 ` Thomas Wolff
2020-07-18 17:45 ` Brian Inglis
2020-07-18 19:37 ` Brian Inglis [this message]
2020-07-18 19:47 ` Brian Inglis
2020-07-18 20:09 ` Achim Gratz
2020-07-18 20:38 ` Brian Inglis
2020-07-18 20:01 ` Achim Gratz
2020-07-18 19:56 ` Achim Gratz
2020-07-18 20:09 ` Thomas Wolff
2020-07-20 6:00 ` Mark Geisert
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=4ace67ed-914f-3107-7f4f-74b11c83c056@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).