I don&#39;t believe there&#39;s any problem with using both.<br>You can use the system package manager to install the compiler and add-on manager, and then use that add-on manager to install all the add-ons for that language you want.&nbsp; That seems to be the setup for most distros.<br>
<br>I just use yaourt -S to install everything -- I like only having to know the syntax for one tool, to deal with everything on the system.&nbsp; I don&#39;t see much of a reason for using cabal-install, as everything I can think of on hackage is also installable by yaourt -S.&nbsp; Also, using the system tool, it tracks which files on your system are owned by which package, tracks when new upgrades are available for your packages, and handles dependencies on non-haskell packages.<br>
<br>There was just an Arch Haskell blog entry on this:<br><a href="http://archhaskell.wordpress.com/2009/02/16/arch-haskell-news-feb-16-2009/">http://archhaskell.wordpress.com/2009/02/16/arch-haskell-news-feb-16-2009/</a><br>
<br>If cabal-install messes with a package previously installed with Arch tools, I think the system tool would complain about the package files being messed with if the system tools are doing a package remove.&nbsp; I haven&#39;t seen an &quot;uninstall&quot; function for cabal-install?<br>
<br>I think of yaourt mostly just as a wrapper for cabal, that provides a consistent interface for all the dependencies on my system (just wish it wrap all the latest ruby gems that way, too).&nbsp; Oh, if for some reason yaourt happens to not have the most recent version of something you want, you can just edit the version number and tarball address in the PKGBUILD when it asks you.<br>
<br>-Leif Warner<br><br><div class="gmail_quote">On Fri, Feb 20, 2009 at 6:18 AM,  <span dir="ltr">&lt;<a href="mailto:papa.eric@free.fr">papa.eric@free.fr</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello... a newbie question (not installed Arch yet, only decided to give it a try... new to this list, too) :<br>
<br>
It seems that haskell packages on Arch can be reliably managed by either cabal-install or arch packages.<br>
<br>
I suppose that mixing both is is not recommended ? e.g. using an arch package if it exists else caba-install, or obtaining one by arch yaourt but then upgrading it by cabal install...<br>
<br>
So, what would be the drawback of installing as arch packages the minimum to have GHC and cabal-install, and then using exclusively cabal-install to install and upgrade haskell stuff ? What does arch packages bring more than cabal-install, since both manage dependences ?<br>

<br>
Thanks, and sorry if the question is naive...<br>
Eric<br>
_______________________________________________<br>
arch-haskell mailing list<br>
<a href="mailto:arch-haskell@haskell.org">arch-haskell@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/arch-haskell" target="_blank">http://www.haskell.org/mailman/listinfo/arch-haskell</a><br>
</blockquote></div><br>