<div dir="ltr">good to know! (i'm out of date on my python knowledge)<div><br></div><div style>I think we're getting pretty far afield.</div><div style><br></div><div style>speaking as someone who's played "OS X support guru/<b>grunt</b>" for people dealing with GHC 7.6 + xcode 5 quite a bit for the past 2-5 months, </div>
<div style><br></div><div style>I don't care about what the release is, as long as we clearly communicate to people </div><div style><br></div><div style>1) xcode 5 + ghc 7.6.3 have issues which require menial intervention and following directions to fix (I even sent out an email giving direction <a href="http://www.haskell.org/pipermail/haskell-cafe/2013-September/110320.html">http://www.haskell.org/pipermail/haskell-cafe/2013-September/110320.html</a> ). The directions i listed don't cover every *correct* way to work around the issues, they merely list the solutions that are easy to communicate and follow. </div>
<div style><br></div><div style>2) how to cope while we get a patched ghc/HP ready (by following directions)</div><div style><br></div><div style>3) get a patched GHC/HP out.</div><div style><br></div><div style><br></div>
<div style>nearly every day I'm helping someone on IRC deal with this issue, and I strongly suspect that thats the tip of the iceberg.</div><div style><br></div><div style>We need to have clear information / warning to people who are installing 7.6 ghc or current haskell platform on OS X about this issue, if we fail to make information about these issues available to new users, some will just give up on bizarre CPP errors and move on. Which i consider unacceptable :)</div>
<div style><br></div><div style>I don't care what solution we do, just that we fix this issue proactively. </div><div style><br></div><div style>while we prep to sort this out, can we at least more clearly link to this issues information on the GHC / HP download pages? I'm really really really really tired of playing support on this issue after a few months of it.... it stopped being fun a month ago when it started happening to people who can't patch their own GHC. We need to deal with this. Also i'm a bit buried with my own stuff this month so i'm worried some people wont' get helped!</div>
<div style><br></div><div style>-Carter</div><div style><br></div><div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Oct 14, 2013 at 2:55 AM, Bob Ippolito <span dir="ltr"><<a href="mailto:bob@redivi.com" target="_blank">bob@redivi.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Monday, October 14, 2013, Dag Odenhall wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><p style="margin:1.2em 0px!important">On Mon, Oct 14, 2013 at 12:20 AM, Brandon Allbery <<a>allbery.b@gmail.com</a>> wrote:</p>
<p style="margin:1.2em 0px!important"></p><div><p></p><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Nope. Arch is a rolling release distribution whose policy is directly opposed to the "stable release" philosophy of the Platform. They will package latest versions of everything, not a "stable release". You *cannot* satisfy their requirements with the Platform; ignore them.</blockquote>
<p></p></div><p style="margin:1.2em 0px!important"></p>
<p style="margin:1.2em 0px!important">I would say it depends on what you mean by “latest”, since one answer could be “latest haskell-platform”. Does Arch Linux ship the latest Python packages, even if an older version is included in the stdlib of the latest Python release?</p>
</div></div></blockquote></div></div><div>There isn't a separate "Python" and "Python Platform". Packages that ship with Python are maintained in Python's repository. Those that are also maintained separately usually have another package/module name altogether so both can be installed without interfering with one another. </div>
<span class="HOEnZb"><font color="#888888">
<div><br></div><div>-bob</div>
</font></span><br>_______________________________________________<br>
ghc-devs mailing list<br>
<a href="mailto:ghc-devs@haskell.org">ghc-devs@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/ghc-devs" target="_blank">http://www.haskell.org/mailman/listinfo/ghc-devs</a><br>
<br></blockquote></div><br></div>