If you use yaourt to install Haskell packages from AUR, it should pull in any needed dependencies that exist as Arch packages. Haskell packages that are only an executable should have no run-time dependencies (no Haskell ones anyway), so you're free to uninstall any Haskell packages that were built as dependencies. If you're using the arch-haskell binary repo, it won't install any build-time dependencies, anyways.

If there's programs that need dependencies in versions not provided by arch-haskell, we could try to fix it, but you might just have to cabal-install it.

You can of course, only use cabal-install for all your Haskell packages, and only use Arch packages for providing e.g. Haskell Platform, if you don't wish to manage your Haskell packages as Arch packages. I go this route with Ruby gems.

-Leif Warner

On Mon, Mar 28, 2011 at 2:49 PM, Mathew de Detrich <deteego@gmail.com> wrote:

Well basically the point would be that libraries would be installed through cabal install however haskell binaries you would install through AUR, and the PKGBUILD would (indirectly through some shell script) check for dependencies, and if a library isn't installed it would temporarily install it in /tmp where the PKGBUILD would link it with ghc to build the binary.

Obviously as mentioned earlier, it's not really an isssue now, but when more widely used haskell binaries are on AUR, if people installed packages thorough cabal and not AUR, something along these lines will need to be done

On 29 Mar 2011 05:07, "Rémy Oudompheng" <remyoudompheng@gmail.com> wrote:

_______________________________________________
arch-haskell mailing list
arch-haskell@haskell.org
http://www.haskell.org/mailman/listinfo/arch-haskell