[MacPorts] #53061: i386-mingw32: remove ports, replaced by i686-w64-mingw32

[MacPorts]

#53061: i386-mingw32: remove ports, replaced by i686-w64-mingw32
-------------------------+-------------------------------------------------
 Reporter:  mojca        |      Owner:
     Type:  enhancement  |     Status:  new
 Priority:  Normal       |  Milestone:
Component:  ports        |    Version:
 Keywords:               |       Port:  i386-mingw32-binutils
                         |  i386-mingw32-gcc i386-mingw32-libunicows
                         |  i386-mingw32-runtime i386-mingw32-w32api
-------------------------+-------------------------------------------------
 I would like to suggest removal of the following ports:

 * i386-mingw32-binutils
 * i386-mingw32-gcc
 * i386-mingw32-libunicows
 * i386-mingw32-runtime
 * i386-mingw32-w32api

 since the functionality is now provided by the new MinGW-w64 ports (see
 #40174):

 * i686-w64-mingw32-binutils
 * i686-w64-mingw32-headers
 * i686-w64-mingw32-crt
 * i686-w64-mingw32-gcc-bootstrap
 * i686-w64-mingw32-gcc

 * x86_64-w64-mingw32-binutils
 * x86_64-w64-mingw32-headers
 * x86_64-w64-mingw32-crt
 * x86_64-w64-mingw32-gcc-bootstrap
 * x86_64-w64-mingw32-gcc

 Some build instructions are here:
 * http://www.mingw.org/wiki/HostedCrossCompilerHOWTO
 * http://www.mingw.org/wiki/linuxcrossmingw
 but note the citation:
 > As of this writing, the MinGW Project does not support any official
 build of GCC, more recent than GCC-3.4.5, for use as a cross hosted MinGW
 development tool, on any platform. This is unlikely to change, until after
 an officially supported stable GCC-4.x version has been released, for
 native use on the MS-Windows platform.
 >
 > If you wish to experiment with more recent versions, then please feel
 free to do so, /.../
 > However, please understand that we are currently unable to offer you
 support for such experimental builds in production use.

 While they don't say it's impossible to use a newer compiler, using GCC
 3.4.5 is literally useless today, and using a newer compiler is both
 unsupported and much more tricky to get working that by simply fetching
 MinGW-w64 that supports using basically any given GCC compiler without any
 patches/modifications at all.

 See also #31578.

 We have no dependent ports other than wxmsw that most likely nobody uses.

 The most we could hypothetically do is provide symlinks from
 `i386-mingw32-gcc` to `i686-w64-mingw32-gcc` etc. I'm not sure if that is
 too helpful though.

 I'm not sure if the ports should be deleted or `replaced_by`. Given that
 the new ports provide different binary names, it might be better to delete
 them.

 If anyone objects, please speak now.

--
Ticket URL: <https://trac.macports.org/ticket/53061>
MacPorts <https://www.macports.org/>
Ports system for macOS