drscheme and mzscheme are built from the same source and drscheme really needs the same version of mzscheme running underneath it. I suspect it needs the same version present for the installation and byte-compiling and so on, but I've not looked closely at this package for a while. Does that answer your question about what it's trying to achieve?
Going back further, I think there we had "overlapping" packages at one point, which is why there was the Provide and Replaces thing going on. The upstream source used to make it easy to build mzscheme or drscheme-including-mz but not drscheme-to-run-on-already-installed-mz. What's the status of this bug? I can't see surviving problems, but I don't have an system to test this upgrade on (yet). -- MJ Ray (slef), K. Lynn, England, email see http://mjr.towers.org.uk/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
