From: Isidor Z. <mi...@qu...> - 2010-06-17 23:43:00
|
> On date Thursday 2010-06-17 09:52:53 -0400, Charles Wilson wrote: > [...] > > It comes down to available manpower and time. The core devs are tapped > > out; look how long it's taking to get mingw-get out the door -- and even > > there, we have a mega-thread from non-core-devs about writing python > > scripts to install msys/mingw "in the interim until mingw-get is ready" > > -- INSTEAD OF ACTUALLY HELPING TO GET MINGW-GET READY. Insanity. > > Hi Charles, > > first of all I want to thank you mingw guys for the time and effort > spent on this project. > > Current installation of MinGW/MYSY is quite painful and possibly > scaring away many potential users and contributors, documentation also > lacks so it has not been immediate for me to arrive at mingw-get. > It's the same for me. I fear the way mingw strives for being self-hosting might split the community too much to allow for huge amounts of contributions. At least from my point of view. I use mingw to cross-compile from Linux, but I had working packaging before (I think most Linux deployments have), so it was just much easier to adapt the existing packaging for a new cross-compile target than to set up a completely separate development environment for mingw. I would love to see a deployment infrastructure which is suitable for self-hosting and integration in cross-compile environments with the same codebase. Maybe yum/rpm ports. Best regards, Isidor |