Re: [Mingw-users] Current Mingw installed "current" option

[Keith M. <kei...@us...>]

On Fri, 2007-10-19 at 07:11 -0400, Earnie Boyd wrote:
> > OK.  Question:  can a user create his own local ini file and direct
> > the installer to use that one?
> 
> I noticed Keith's response, I would imagine that you could modify the 
> mingw.ini after the point the installer downloads the one from 
> mingw.org.

Yes, if you let the installer complete its `checking for updates' phase,
then leave it sitting at the `welcome' screen, you can edit or replace
the mingw.ini file with your own variant, then allow the install to
continue with that; hardly user friendly, though.

> I thought there were some heuristics in the script to check the Build
> value of the mingw.ini file to determine whether mingw.ini should be
> replaced; I don't remember the details.

There may be, but they certainly don't check if a *locally* pre-existing
mingw.ini has a greater build number than either the embedded copy, or
the downloaded one.  IMO, this *should* be checked, so, yet another bug.

Additionally, having persuaded the installer that a `current' install
should provide binutils-2.17.50 and gcc-3.4.5, a subsequent run reverted
those to binutils-2.16.91 and gcc-3.4.2, without bothering to check the
installed versions recorded in installed.ini, and noting that they were
more recent.

This is so totally screwed up, is it any wonder there are so many of us
who prefer to install manually?

Regards,
Keith.