On Tue, Mar 15, 2005 at 09:24:09PM +0000, Ian Lynagh wrote:
I would say there is no need to do that, since we can just depend on ghc and get the right thing, like we do now.
But shouldn't the tool to make debs from cabal packages automatically build-dep on things the cabal package says it needs? Doing the above would mean we don't need to special case it for that list.
Well, my tool doesn't automatically build-dep on anything; the user still has to craft debian/control like usual. No idea if anyone else has a tool...
I don't think you really need to. A Provide is only useful if there are several ways to satisfy a dependency, which there really aren't here.
This would also mean things would keep on working if (in at least one case, when) bits get split out from ghc6 into their own package.
Assuming people build-dep on the provided packages now, but really, I'm not sure that there's any call to split most of those out. I could see a ghc and a ghc-nox, I guess.
-- John