Earnie Boyd <earnie_boyd@...> writes:
> I've been contemplating the next MinGW release. I'm wondering if I
> shouldn't just package MSYS within this release. So here is the next
> [ ] Sounds great, do it.
> [X] Sounds stupid, why would you ever to that?
> [ ] Sounds great, but 3 more mega byte for MinGW, ouch!
> [ ] Other opinion __________________________________.
A number of reasons:
1. I like to install mingw and msys in 2 completely independent
directories - I can't see a combined package offering that (unless
it prompts for each location independently).
2. Users who don't need msys will run the new installer, and will see
the msys icon as the only evidence of what has happened. If they
try it, they'll get completely the wrong idea of what mingw is...
3. I suspect *many* people will be quite happy with just mingw - msys
for them will just be (potentially) confusing bloat. Unfortunately,
I suspect that the proportions on the lists (and hence the audience
for your question) will be strongly biased towards people who *do*
use mingw. (But this is just speculation on my part...)
I know that I have friends who I give the mingw package to, but who
would have no interest in, or use for, msys.
I'd suggest that you do a mingw-only distribution and a combined
distribution, but that isn't likely to give enough benefit to be worth
If you go for a combined installer, I'll probably end up installing
once, unpicking the 2 parts, and building my own separate packages.
(And giving the mingw one to my friends in preference to directing
them to the official site...)
This signature intentionally left blank