On Tue, 15 Mar 2005, John Goerzen wrote:
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...
One could imagine an improved or alternate tool being constructed in future, though. Doing this now will make life easier in future if such a thing emerges.
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.
I would be in favour of adding the provides now so that the flexibility to split things out in future is there.
Cheers,
Ganesh