cabal2arch 0.6: now builds haddocks for libraries
http://aur.archlinux.org/packages.php?ID=17471 Thanks Magnus for the patch. Note this means ghc <=> haddock need to stay in sync. -- Don
Don Stewart wrote:
http://aur.archlinux.org/packages.php?ID=17471
Thanks Magnus for the patch. Note this means ghc <=> haddock need to stay in sync.
Cool. On a somewhat related note. Is someone keeping track of what version of cabal2arch was used to "Arch-ify" what haskell packages? (Or is there a way to ask AUR about it?) I'm not saying all packages should be re-processed *every time* cabal2arch is upgraded, but it might be worth doing for *some* upgrades to cabal2arch. Adding building of docs could be one time when it's justified to re-run cabal2arch over all packages on Hackage. If we in the future add building of profiling then that might also be reason to do the same. /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus＠therning．org Jabber: magnus＠therning．org http://therning.org/magnus identi.ca|twitter: magthe
magnus:
Don Stewart wrote:
http://aur.archlinux.org/packages.php?ID=17471
Thanks Magnus for the patch. Note this means ghc <=> haddock need to stay in sync.
Cool.
On a somewhat related note. Is someone keeping track of what version of cabal2arch was used to "Arch-ify" what haskell packages? (Or is there a way to ask AUR about it?)
I'm not saying all packages should be re-processed *every time* cabal2arch is upgraded, but it might be worth doing for *some* upgrades to cabal2arch. Adding building of docs could be one time when it's justified to re-run cabal2arch over all packages on Hackage. If we in the future add building of profiling then that might also be reason to do the same.
The PKGBUILD lists the version. At the moment I update only when the package updates on hackage. We might want a different policy. -- Don
magnus:
Don Stewart wrote:
http://aur.archlinux.org/packages.php?ID=17471
Thanks Magnus for the patch. Note this means ghc <=> haddock need to stay in sync.
Cool.
On a somewhat related note. Is someone keeping track of what version of cabal2arch was used to "Arch-ify" what haskell packages? (Or is there a way to ask AUR about it?)
I'm not saying all packages should be re-processed *every time* cabal2arch is upgraded, but it might be worth doing for *some* upgrades to cabal2arch. Adding building of docs could be one time when it's justified to re-run cabal2arch over all packages on Hackage. If we in the future add building of profiling then that might also be reason to do the same.
The status script lists this: http://www.galois.com/~dons/arch-haskell-status.html Column 5.
participants (2)
-
Don Stewart -
Magnus Therning