What could be done is letting the community rate the quality of the modules for each platform? Maybe with user comments? Like <a href="http://amazon.com">amazon.com</a> (so we <a href="http://hackazon.org">hackazon.org</a> ;-) And using lambdas instead of stars for giving the rating :)<div>
<div><div><div><div><div><div><div><div><br><br><div class="gmail_quote">On Tue, Jan 13, 2009 at 6:13 PM, Don Stewart <span dir="ltr"><<a href="mailto:dons@galois.com">dons@galois.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Well, the number one thing is to use Cabal and the cabal-install tool.<br>
That is the simplest way to avoid headaches.<br>
<br>
Regarding libraries in general, the platform project is underway, aiming<br>
to bless a set of stable, "batteries included" packages, saving<br>
duplicated work determining which, say, json library to use.<br>
<br>
-- Don<br>
<br>
<br>
jamiiecb:<br>
<div><div></div><div class="Wj3C7c">> I agree completely. There is not nearly enough documentation on<br>
> packaging in haskell and too many hackage packages are broken or do<br>
> not install. I know several people are working on improving this but<br>
> they seem do be doing so rather quietly. Could someone briefly outline<br>
> what improvements are planned and what stage the current work is at? I<br>
> remember seeing some demos at anglohaskell during the summer but<br>
> nothing since.<br>
><br>
> Jamie<br>
><br>
> On Tue, Jan 13, 2009 at 3:33 PM, Regis Saint-Paul<br>
> <<a href="mailto:regis.saint-paul@create-net.org">regis.saint-paul@create-net.org</a>> wrote:<br>
> > Hi,<br>
> ><br>
> > I've seen many times the monad topic coming around on the cafe and plentiful<br>
> > tutorials on monads have been published. However, as a complete Haskell<br>
> > newbie coming from OOP, I felt monads were not particularly difficult to<br>
> > grasp, and very exciting to work with.<br>
> ><br>
> > During my experiments with Haskell so far, the main problems I kept bumping<br>
> > into were not related to the language but to its libraries: their<br>
> > compilation and installation. Unfortunately, this topic has not received<br>
> > nearly as much attention. I was unable to find a comprehensive tutorial on<br>
> > how to deal with the variety of problems I get when trying to install<br>
> > Hackage packages. This turned out to be (and still is) THE main source of<br>
> > wasted time and headaches. And worse, unlike type problems, these are not<br>
> > interesting ones to solve.<br>
> ><br>
> > Thus, as a beginner, the package management is what is really getting in the<br>
> > way of switching to Haskell--not the language. Even books like Real World<br>
> > Haskell (otherwise excellent) ignore entirely the topic. Cabal and<br>
> > Cabal-install are clearly wonderful applications that make installing most<br>
> > packages very straightforward. Unfortunately, whenever this "standard"<br>
> > method for package installation fails (or when it is not available as with,<br>
> > e.g., gtk2hs), I find myself in complete disarray.<br>
> ><br>
> > Below are some of the questions and issues I faced regarding package<br>
> > management:<br>
> ><br>
> > - For a number of packages, cabal-install gets stuck and has to be killed. I<br>
> > assume this is due to some difficulties in solving the dependencies and it<br>
> > is fine, not all can be automated and cabal-install is not responsible for<br>
> > poor packages. But the question then becomes what to do from there? Is their<br>
> > some method to solve dependencies? How should we proceed to "debug" a<br>
> > package installation? How do gurus deal with that? (maybe some less known<br>
> > command line arguments? Or ways to figure out the problem and work out its<br>
> > solution (cabal-install is silent in such case)? In particular, how to know<br>
> > why did cabal get stuck in the first place?<br>
> ><br>
> > - Some packages on Hackage are reported as not building successfully with<br>
> > GHC6.10 (e.g., encoding) while others do not build with 6.8 (e.g., salvia)<br>
> > and the later might depend on the former...What is one supposed to do in<br>
> > such case? For example, is it an appropriate way to proceed to compile a<br>
> > package with one version of GHC and then use the compiled package with<br>
> > another version of GHC? Is it safe? What could possibly go wrong? If it is<br>
> > the right way to go, how should we setup the two GHC versions? For instance,<br>
> > should we have a shared package configuration file and choose through the<br>
> > path which GHC is used or is there nicer way to set this up?<br>
> ><br>
> > - Taking for example the "encoding" package on Hackage. Last time I tried,<br>
> > the log was saying it fails to build on GHC 6.10, however, looking inside<br>
> > this Hackage log, I could see a successful compilation using "preferred<br>
> > versions". So it looks as if the thing can be compiled somehow. What should<br>
> > one do with this information? If cabal manages to compile it using this<br>
> > method on Hackage, then isn't cabal install just doing it on my disk? Is it<br>
> > possible through some command line? Is it possible manually (without<br>
> > cabal-install) and, if so, how? (I tried to copy-past the build instruction<br>
> > as it appeared on the log...that somehow compiled, but then, I failed to<br>
> > figure out how to install...)<br>
> ><br>
> > - I'm primarily a windows user and lots of my initial struggles probably<br>
> > came from that. After many difficulties, I figured out that installing MinGW<br>
> > and MSys was *THE* way to get a bit more of the things working. First, a lot<br>
> > of time would be saved by just saying clearly on the GHC download page that<br>
> > MinGW and MSys are mandatory installation (or even package that with GHC for<br>
> > the windows distribution if license allows, who cares the extra few Mb).<br>
> > Even if that is not technically exact, i.e., even if ghci and many trivial<br>
> > command line programs can work without, MSys and MinGW turn out to be quiet<br>
> > necessary whenever trying to install anything producing side effect. Making<br>
> > it plain that these two are necessary would real come has a great time<br>
> > savers for newbie like me on windows (personal opinion of course). Or, if<br>
> > another path exists to go without these two, I'd be very glad to learn.<br>
> > Besides, even these tools basic installation is not enough, you need<br>
> > automake and various things of the like. That makes me wonder if the most<br>
> > precious skill for programming with Haskell would not be a strong C/C++<br>
> > programming background.<br>
> ><br>
> > - In face of the difficulties with windows, I switched to Linux. While some<br>
> > things worked better, there were still lots of difficulties with package<br>
> > compilation. For instance, it is very difficult to figure out which Linux<br>
> > packages of a given distribution are needed for compiling this or that<br>
> > package. Again, gtk2hs is epitome here: which C development packages are<br>
> > needed to compile it is obscure at best (cairo, codeview, etc...). I ended<br>
> > up querying the Debian package management with any keyword found after<br>
> > running gtk2hs and randomly installing all the dev packages...And when<br>
> > gtk2hs finally compiled, it failed to install anyway. As of today, I've<br>
> > never been able to compile even the dumbest demo using gtk2hs whether on<br>
> > linux or on windows and whether using ghc 6.8.3 or 6.10.1. On windows, the<br>
> > automated setup install worked but did not allow me to compile with codeview<br>
> > and I still do not know how to add codeview to the install packages. Trust<br>
> > that I tried hard and read the docs thoroughly. Gtk2hs is just on of many<br>
> > examples; I had problems under Linux also with, e.g., Happs, yi, database<br>
> > things, etc. and figured out that the situation was roughly identical to<br>
> > windows with MSys and MinGW. So Linux appears not to be the right solution<br>
> > here. Maybe it's just that Linux users are more experienced with the GNU<br>
> > C/C++ libraries...but it won't help a windows user to switch to Linux since<br>
> > this knowledge can't be built out of thin air.<br>
> ><br>
> > - Would there be some binary version of cabal targeting various OSs? I<br>
> > believe the Haskell platform project is about that. But without waiting for<br>
> > a fair and objective selection of the packages (it seems to be the current<br>
> > status of the project), I'd be happy working with some authoritative bundle<br>
> > produced by a Haskell guru and would trust his subjective choices (who am I<br>
> > to question these choices anyway). Or even an image (e.g., virtual box or<br>
> > Xen) of a fully setup development environment since there are so many<br>
> > dependencies involved in, e.g., simply compiling GHC...<br>
> ><br>
> > Now, one might argue that these are not Haskell problems, that they are<br>
> > normal when dealing with non-mature packages. So let me explain why I've<br>
> > been trying hard to install these packages:<br>
> ><br>
> > As a beginner with no experience with emacs, I tried to find some IDE-like<br>
> > environment which would, at least, save me from manually reloading files in<br>
> > ghci or help me browse the source files. Following the Haskellwiki advice,<br>
> > that led to trying out Yi, Leksah, eclipsefp, or a Visual Studio extension.<br>
> > To this date, NOT ANY SINGLE ONE of these worked, be it on Linux or Windows.<br>
> > I had to resort to learning emacs which seems the only sensible choice<br>
> > available today.<br>
> ><br>
> > I am particularly unskilled, no question here. But, would a charitable soul<br>
> > take the pain of writing a comprehensive package management tutorial instead<br>
> > of a monad one, (s)he would have my deepest gratitude :)<br>
> ><br>
> > Apologies for the long mail.<br>
> ><br>
> > -Regis<br>
> ><br>
> > P.S. People on #haskell are wonderful. They helped me solve many issues.<br>
> > Unfortunately, solving specific instances of problem did not contribute much<br>
> > to a deeper understanding of the internal working. I find myself randomly<br>
> > trying things without knowing which would work or why; Hence this plea for a<br>
> > tutorial.<br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Haskell-Cafe mailing list<br>
> > <a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
> > <a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
> ><br>
> _______________________________________________<br>
> Haskell-Cafe mailing list<br>
> <a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
> <a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
</div></div></blockquote></div><br></div></div></div></div></div></div></div></div></div>