[arch-haskell] cabal2arch 0.6.1 now generates bad dependencies
dons at galois.com
Sat Jan 16 15:24:10 EST 2010
> * On Saturday, January 16 2010, Don Stewart wrote:
> >Right, that's the usual 'ghc major update' diff.
> >I'll take care of it. The list just has to match this page:
> > http://haskell.org/haskellwiki/Libraries_released_with_GHC
> >-- Don
> It might be sensible to remove the use of corePackages in:
> ] removeCoreFrom :: [Dependency] -> [Dependency]
> Considering the current ghc now provides haskell-* packages for all of
> it's core libraries:
> Provides : haskell-array=0.3.0.0 haskell-bytestring=0.9.1.5 haskell-cabal=22.214.171.124
> haskell-containers=0.3.0.0 haskell-directory=126.96.36.199
> haskell-extensible-exceptions=0.1.1.1 haskell-filepath=188.8.131.52
> haskell-haskell98=184.108.40.206 haskell-hpc=0.5.0.4
> haskell-old-locale=220.127.116.11 haskell-old-time=18.104.22.168
> haskell-pretty=22.214.171.124 haskell-process=126.96.36.199 haskell-random=188.8.131.52
> haskell-syb=0.1.0.2 haskell-template-haskell=184.108.40.206
> haskell-time=1.1.4 haskell-unix=220.127.116.11 haskell-utf8-string=0.3.4
> That would make all library dependencies explicit (well other than
> base). If ghc continues to reduce the set of core libraries (ex. mtl is
> missing from 6.12), pkgbuilds will have to be updated less frequently.
Oh, that's an interesting idea. It moves the list to keeping ghc's list
up to date. Which I presume happens every time we update ghc?
Where does the list of what our ghc package provide live? Maybe I can
just suck that in?
> But perhaps such a change isn't worth the extra time pacman will then
> take to resolve dependencies... and also other bugs in yaourt it might
That's always a risk.
More information about the arch-haskell