Re: [Plplot-devel] Planning for the release of 5.13.0

[Alan W. I. <ir...@be...>]

On 2017-08-15 11:03-0000 Arjen Markus wrote:

>> -----Original Message-----
>> From: Alan W. Irwin [mailto:ir...@be...]
>> Sent: Tuesday, August 15, 2017 12:42 PM
>> To: Arjen Markus
>> Cc: PLplot development list
>> Subject: RE: [Plplot-devel] Planning for the release of 5.13.0
>>
>> On 2017-08-15 08:03-0000 Arjen Markus wrote:
>>
>>> I expand the path to get access to git in the comprehensive tests, but then
>> CMake fails:
>>
>> Hi Arjen:
>>
>> How do you expand the PATH?  If you mean put /usr/bin on it, doesn't that already
>> happen automatically when you set the appropriate shell for MinGW-w64/MSYS2?
>>

> Oh, don't worry: when you start a MinGW-w64/MSYS2 shell or a Cygwin
shell for that matter, you get a dedicated path variable. In fact much
cleaner than the one a DOS-box starts with, as that accumulates a lot
of junk :(. I had to expand it to get access to git - it resides in
"c:\program files\git" and that is not part of the initial path.

> Meanwhile, leaving out "git" has allowed CMake to continue without
much ado - CMake encounters a wxWidgets directory within the git
installation, but without the header files and then chokes, it seems.

> For now I run the tests without git.

That sounds like absolutely the correct approach since from its
location the above version of git is obviously not part of the
MinGW-w64/MSYS2 platform (which is a big strike against that version
of git right from the start), and you further discovered including
"c:\program files\git" on your PATH brings additional problematic
baggage.

In fact, in the interest of getting these tests done as quickly and
easily as possible, let's forget about git on MinGW-w64/MSYS2 entirely
until after this release, i.e., when your current test with git
completes, please send me that report tarball, and with luck (no
showstopper issues revealed) that should be the last noninteractive
test you need to do for this platform before the 5.13.0 release.

But please also copy the following ideas to your post-release ToDo list
for MinGW-w64/MSYS2.

Try using the

pkgfile git.exe

command to discover the names of the installed and uninstalled
MinGW-w64/MSYS2 packages that contain git.exe.  Assuming that works
(and you have previously assured me your tests show that pkgfile does
work to reliably search installed and uninstalled packages for filenames), then
I am virtually positive that one of those package names will be "git"
without a prefix, i.e., it is part of the "msys2" repository rather
than the "mingw64" repository.  Then according to
<https://wiki.archlinux.org/index.php/Pkgfile>
you should be able to use

pkgfile -l <package name>

e.g.,

pkgfile -l git

to list all files in the git package.  One of those should be
/usr/bin/git.exe so after you install the git package, then

hash git; hast -t git

should respond with /usr/bin/git.exe, and that should finish off this
distracting subtopic of which git version to use for the
MinGW-w64/MSYS2 platform.

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state
implementation for stellar interiors (freeeos.sf.net); the Time
Ephemerides project (timeephem.sf.net); PLplot scientific plotting
software package (plplot.sf.net); the libLASi project
(unifont.org/lasi); the Loads of Linux Links project (loll.sf.net);
and the Linux Brochure Project (lbproject.sf.net).
__________________________

Linux-powered Science
__________________________