Op do, 20-04-2006 te 16:39 -0500, schreef John Goerzen: > OK. I can see that. However, I don't want to restrict > haskell-devscripts to working with only one version of Cabal. It is up > to the package maintainers to depend on the version of Cabal they want, > and to conflict on the version they don't want. There is no code in > haskell-devscripts that is putting different paths there; this must be a > change in Cabal. That makes sense.
> > > So I'm not sure what I'm supposed to do here. Are you simply suggesting > > > I should change the Depends line to omit libghc6-cabal-dev, which is > > > indeed outdated? If so, I have no problem with doing that. > > > > Well I would suggest to replace the Depends line to omit ghc6 instead. > > That way you depend on the latest Cabal version. But removing the > > That would be bad; it would leave no way for people to build packages > with the current Cabal version in ghc6. Hmm, you are right. > > libghc6-cabal-dev would be fine be me as well. > > OK, I think I'll do that. That makes sense. Yep, that seems to be the most reasonable thing to do. There still can occur some problems though. If I build a package on a system without libghc6-cabal-dev but one of the autobuilders has libghc6-cabal-dev installed, the installation directories will change. This can only be solved by specifying the specific cabal implementation you want using Build-Depends and Build-Conflicts. Sign. Maybe this should be documented in a README? It seems that the difference in behaviour will be solved soon anyway. From the documentation of ghc 6.4.2: Cabal has been upgraded to version 1.1.4. Anyway, thanks for your input Greetings Arjan
signature.asc
Description: Dit berichtdeel is digitaal ondertekend
