<br>On Fri, Jun 10, 2011 at 03:15, Manuel M T Chakravarty wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Ian Lynagh:<br>
<div>> On Mon, Jun 06, 2011 at 03:47:57PM +0100, Malcolm Wallace wrote:<br>>> On 6 Jun 2011, at 13:49, Lyndon Maydwell wrote:<br>>>> I would be fantastic if XCode wasn't a dependency. ...<br>
>>><br>
>>> Not to detract at all from the work of the wonderful GHC and Haskell<br>
>>> Platform contributors in any way. For me it would just make it that<br>
>>> much easier to convince mac-using friends to give Haskell a try.<br>
>><br>
>> The ghc team already bundle a copy of gcc in their Windows distribution, precisely because it can be fiddly to get a working copy of gcc for that platform otherwise. I wonder if they would consider the possibility of shipping gcc on Mac too? (There may be good reasons not to do that, but let's have the discussion.)<br>
><br>
> I'm pretty sure we aren't allowed to redistribute XCode.<br>
><br>
> As well as gcc and friends, I think XCode also includes various headers<br>
> and/or libraries that we need.<br>
><br>
> If there is an alternative - especially one that allows us to support<br>
> multiple versions of OS X more easily - then using it may make sense.<br>
<br>
</div>You are right, the Xcode install includes many tools as well as headers etc.<br>
<br>
What would be the advantage of including gcc and all these other things in GHC?</blockquote><div><br></div><div>To simplify the process of installing GHC and to support people with versions of Mac OS X older than the most current. We want to spread the Haskell love as far as possible.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Anybody who is halfway serious about developing software on a Mac will have Xcode installed anyway.</blockquote>
<div><br></div><div>You could say the same about people halfway serious about developing software on Windows. But GHC doesn't require you to install MinGW, Cygwin, or Virtual Studio.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Besides, as Xcode updates are now available from the Mac App Store,</blockquote><div><br></div><div>Not for older versions of Mac OS X.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
you don't even need to register as a developer with Apple anymore — yes, you need to pay the nominal $5 for the 4GB download. If you don't want to do that, install the (probably older) version of Xcode that came with the install DVDs of your Mac.<br>
</blockquote><div><br></div><div>This doesn't solve the problem if the GHC package only supports later versions of Xcode. There has already been at least one difference between Xcode 3 and 4 ( <a href="http://hackage.haskell.org/trac/ghc/ticket/5011">http://hackage.haskell.org/trac/ghc/ticket/5011</a> ) that caused a problem and there may be others in the future.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I don't think you can compare this with the situation on Windows. Microsoft does not distribute a canonical set of Unix tools that all developers use.</blockquote><div><br></div><div>No, but Cygwin and MinGW are available for free and have been around for a long time. Why does GHC bundle MinGW instead of expecting the user to install it herself? Convenience?</div>
<div><br></div><div>I think there is a clear benefit to supporting older versions of Mac OS X. Not everybody upgrades at the same rate that Apple releases new versions. Indeed, Apple's updates occasionally change architecture requirements or break applications, so some people cannot upgrade.</div>
<div><br></div><div>Having a new package bundling GNU tools/libraries doesn't preclude the current package using Xcode. The only good arguments against a new package, that I can see, are the additional work to develop the packaging and the testing, release, and maintenance efforts. Perhaps there are some compatibility concerns, working with other OS X libraries/applications. Of course, these are not at all insignificant issues, but these are the main concerns.</div>
<div><br></div><div>Regards,</div><div>Sean</div>
</div>