From: Earnie <ea...@us...> - 2010-08-25 15:20:20
|
Jasper Horn wrote: > On Wed, Aug 25, 2010 at 3:46 PM, Keith Marshall wrote: > > Ah, there's your original reply, just a bit delayed... > >> IIRC, that will not help. The current mingw.ini file relates to the >> package payload for GCC-3, as managed by MinGW-5.1.6. The knowledge of >> which packages are required, (quite distinct from which versions of those >> packages to deliver), is hard coded into mingw-5.1.6.exe; (mingw.ini only >> identifies the latest available versions of those pre-specified packages). > > I see. So what about a simple installer based on a manual install > which is archived and will be unarchived into a specified folder when > run? (or perhaps just the archive itself without an installer) > > I would be willing to make it, if you are willing to support it. The > only catch is that it's a pain to maintain it, so I will try do so > when I happen to have time, but without making any promises or stating > that I will continue to do so. I don't know how the mingw team > developers feel about this, but I think even a slightly outdated > installer is better than no installer at all. > That is no different than we have now. It would just be with new files that become outdated. The lack of (or absence of) maintainers is what has us in the sour pickle juice. So if you can't maintain it then we can't offer it because our time is just as limited as yours. -- Earnie -- http://www.for-my-kids.com P.S. A tip of the hat and a round of cheers with raised glass to KHMan for his acknowledgment and respect of our time. |