[OT] Re: There's new GIT instructions on Github now

[Daniel Gibson]

Am 21.05.2011 01:18, schrieb Nick Sabalausky:
> "David Nadlinger" <see at klickverbot.at> wrote in message 
> news:ir6r72$l38$1 at digitalmars.com...
>> On 5/21/11 12:34 AM, Nick Sabalausky wrote:
>>> And again, using Wine doesn't count as supporting Linux, so why the hell
>>> should the other way around be any different?
>>
>> Because, at least in my eyes, there is a huge difference between telling 
>> your users that using Wine they might be able to get your software to work 
>> on Linux (which is typically the most you can hope for if you are a Linux 
>> user), and using MinGW to make porting your application to Windows easier, 
>> which is not necessarily visible to the end user.
>>
> 
> OSS programs, which most Linux programs are, are expected to be compilable 
> by the user. Therefore, if msys or mingw are required to build it, then it 
> *is* visible to the end user.

Compiling on Windows always sucks and is generally not done by the end
*user* (who generally is not a coder).
And I think it's easier for the user to install MinGW and MSYS and run
make than installing and configuring Visual Studio (especially when the
project is for another, maybe older, version) and use that for compiling.

> 
>> (Yes, Wine is occasionally used by software vendors themselves as well, 
>> like in the form of Transgaming Cider by Riot Games for the Mac version of 
>> their League of Legends game, but I hope you'll agree that this is not 
>> what one typically thinks about when Wine is mentioned.)
>>
> 
> So if wine is used to make "porting" a windows program to linux easier 
> (which doesn't have to be visible to the end user - wine can just be 
> packaged together with it), it's a giant blunder and doesn't count. But if 
> an open source linux program is "ported" to windows, and anyone who wants to 
> make any use of it's open source nature is required to use 
> msys/mingw/cygwin, then that's just plain good porting.
> 
>