<div dir="ltr">Thank you for your advice. It's good that I kept it to a minimum; I was thinking to hand to you also the *-conduit stuff, but I've better maintain it myself.</div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Mon, Jul 29, 2013 at 2:03 PM, Magnus Therning <span dir="ltr"><<a href="mailto:magnus@therning.org" target="_blank">magnus@therning.org</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 Sun, Jul 28, 2013 at 12:04:55PM +0200, Magnus Therning wrote:<br>
> On Jul 27, 2013 6:51 PM, "Nicola Squartini" <<a href="mailto:tensor5@gmail.com">tensor5@gmail.com</a>> wrote:<br>
>><br>
>> Hi,<br>
>><br>
>> For those of you interested in Haskell for the web, I created using<br>
>> cblrepo a new repository containing all the latest happstack,<br>
>> clckwrks and gitit packages. If you want to use it, add this to<br>
>> your pacman.conf<br>
>><br>
>> [haskell-happstack]<br>
>> SigLevel = Never<br>
>> Server = <a href="ftp://noaxiom.org/$repo/$arch" target="_blank">ftp://noaxiom.org/$repo/$arch</a><br>
>><br>
>> I believe that some of the dependencies now in haskell-happstack<br>
>> should rather go in haskell-core. Here is a minimal list:<br>
>><br>
>> base16-bytestring<br>
>> haskell-src-meta<br>
>> syb-with-class<br>
>> time-compat<br>
><br>
> Would you mind putting this request in a bug on github/habs instead<br>
> please? It reduces the risk that I forget to deal with it ;-)<br>
<br>
</div></div>I noticed you did what I asked, which is great :) There is just one<br>
thing that I feel I need to point out before I add the packages, and I<br>
think it's better to highlight and keep any possible ensuing<br>
discussion here rather than bury it in a ticket on github.<br>
<br>
By adding these package in [haskell-core] you are relieving yourself<br>
of some of the work with packaging happstack, but you are also handing<br>
over some of the control. If any of the packages added to<br>
[haskell-core] is frequently updated on hackage and the happstack<br>
developers are a bit slow with reacting to new versions of its<br>
dependencies then you are likely to find that at times<br>
[haskell-happstack] isn't usable -- [haskell-core] has moved on, but<br>
[haskell-happstack] can't be rebuilt on top of it yet.<br>
<br>
We've had discussions in the past on how to deal with this, but<br>
nothing's really materialised (probably my fault). We've also not run<br>
into this particular problem terribly often with the only other<br>
auxiliary repo, [haskell-web]. So maybe it's just good that<br>
[haskell-happstack] comes along and forces the issue ;)<br>
<br>
Anyway, this isn't a big deal and I'm sure we can work something out<br>
if it becomes a recurring issue. However, I think you really should<br>
know up front what you are getting yourself into ;)<br>
<span class="HOEnZb"><font color="#888888"><br>
/M<br>
<br>
--<br>
Magnus Therning OpenPGP: 0xAB4DFBA4<br>
email: <a href="mailto:magnus@therning.org">magnus@therning.org</a> jabber: <a href="mailto:magnus@therning.org">magnus@therning.org</a><br>
twitter: magthe <a href="http://therning.org/magnus" target="_blank">http://therning.org/magnus</a><br>
<br>
<br>
Perl is another example of filling a tiny, short-term need, and then<br>
being a real problem in the longer term.<br>
-- Alan Kay<br>
</font></span></blockquote></div><br></div>