<div class="gmail_quote">On Mon, Sep 24, 2012 at 11:37 PM, Fabio Riga <span dir="ltr"><<a href="mailto:rifabio@gmail.com" target="_blank">rifabio@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In data 20.09.2012 17:34:15, Nicolas Pouillard ha scritto:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks it seems to work great!<br>
</blockquote>
Thank you! Please note that this is a test. So expect this to break in some way.<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Can you tell how easy to maintain a repository (cblrepo) on top of the<br>
archhaskell one. I did thought about forking habs but it is a waste of<br>
time. However building another repo on top of it might provide with a<br>
nice distributed nature allowing us to maintain the package we care the<br>
most about.<br>
<br>
Did you took special steps, how do you merge the cblrepo from the main habs?<br>
You turn them from RepoPackages to DistroPackages right?<br></blockquote></blockquote><div><br>Why was this - what looks like a very interesting - message not posted to the list?<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote>
This was exactly my idea. There's no need to fork the excellent work made by Magnus and others. I made a new repo using cblrepo. I inserted the same GhcPkg of habs. Then I made a script for adding new packages, tracking all dependencies using cabal install, and check them with the habs repo. If packages are there, the script uses cblrepo to add them as DistroPkg, else they are inserted as repo.<br>
<br>
The script is far from being completed and usable, and I haven't had enough time to clean, document and publish it. I would like to make it easy to make a new repository tracking many others, not just one. So to make, as you told, a distributed system.<br>
<br>
The main problem I encountered (and everyone using [haskell-extra] will do) is that when a package in [habs] is updated and I have a package installed that depends on it, pacman will refuse to update the system until [haskell-extra] is updated as well. This is unavoidable, as I need the new package in [habs] before updating [haskell-extra]. The alternative would be to recompile all updated packages in [habs] AND all affected package in [haskell-extra], and I won't do this! Another way could be to have updated packages in a private repository for a couple of days, so my repository (and others as well) could have the time to keep in sync. With the latter solution, we could easily merge the resulting packages in one repository.<br>
</blockquote><div><br>If there is a single repository that merges all the real distributed repositiories, that is the only one that needs to be "public".<br>I suggest renaming [haskell] (to haskell-core or haskell-init), and creating the merging repo with the name [haskell] right away, and see if it works for merging current [haskell] and current [haskell-extra].<br>
I hereby offer my server to get this up and running initially (we can move it elsewhere as necessary later).<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I hope this clarify a little what I'm doing. Any suggestion is highly appreciated.<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div><br>My suggestion above to make the merged repo now, and the meta-suggestion to refocus on being inviting so we can easily get more people/resources/time from the community.<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888">
Fabio</font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
arch-haskell mailing list<br>
<a href="mailto:arch-haskell@haskell.org" target="_blank">arch-haskell@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/arch-haskell" target="_blank">http://www.haskell.org/<u></u>mailman/listinfo/arch-haskell</a><br>
</div></div></blockquote></div><br>