[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #57740] 5.2 win installer: wrong behavior with

From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #57740] 5.2 win installer: wrong behavior with icon on taskbar (was fine days before)
Date: Wed, 5 Feb 2020 12:36:38 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Follow-up Comment #18, bug #57740 (project octave):

I think I'm growing weary of building binaries for Windows systems.  :-)

My experience with a delay between source releases and Windows binaries
appearing is people complaining that they don't know what to do with a tar.gz
file on a Windows system.

We should be prepared to make multiple binary releases for the same source
release.  Maybe they should all be in files with names like
octave-5.2.0_0-installer.exe so that we can bump the build number (the "_0"
part of the filename) to distinguish files on the ftp server.  But no matter
what that digit is, they will all be version 5.2.0, based on the 5.2.0 source
release, and any patches specifically for Windows would be identified by the
HG ID of the mxe-octave revision used to build the binary.

Do we need the extra version number for the installer so that multiple 5.2.0
releases can be installed simultaneously?  Probably not.  The reason for it in
the past was that after a release like 5.2.0, we wouldn't bump the version
number to 5.2.1 until the next release.  So people who had installed the
stable release (5.2.0) couldn't easily keep that installed and also install
the next 5.2.N release for testing.  But now that we've modified the version
scheme to go from 5.2.0 (release) to 5.2.1 (dev for 5.3.0 release) I think we
can drop the extra Windows version digit thing.  Then, as I understand it, the
icon association should work again, correct?


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]