* On Saturday, April 25 2009, Don Stewart wrote:
vegai:
On Fri, Apr 24, 2009 at 11:12:56PM -0400, Adam Vogt wrote:
Many packages in [community] remain to be rebuilt against the new ghc.
Perhaps we should depend on specific ghc versions: that way pacman will enforce the dependencies: it won't really reduce the work required to upgrade ghc, but I think that it might be more clear that said installed libraries won't work.
I agree. In fact, my packages in community already do this.
That's an interesting idea. [community] is smaller than AUR, so it may be feasible to tag with the required GHC.
Ok. Here is a simple way to do it by modifiying the package after the fact: #!/bin/sh ghcver=6.10.2 # we could get this from pacman tar xzf "$1" .PKGINFO mv .PKGINFO pkginfo sed "s/^depend = ghc*$/depend = ghc==$ghcver/" < pkginfo > .PKGINFO tar czf "$1" .PKGINFO rm .PKGINFO pkginfo Unfortunately, pacman does not let you specify a specific release version since different releases are unlikely to be binary compatible. Other than changing pacman in that respect (if it doesn't break or change anything else, I can't see there being any problems with that), we could add the release version to the ghc package version (ghc-6.10.2rel2-2), but that is sort of unpleasant.
I don't think this would help AUR, though.
Agreed. With the AUR this problem is much less serious, since those packages are usually installed right after being built (ie, what yaourt does). Another place to check the ghc version is in the register script which could easily contain the full ghc version that the package was built with. That won't affect how pacman chooses which versions to install however. Adam