The dev-lisp/drscheme and dev-lisp/plt ebuilds both install the same set of binaries (or links) in /usr/bin. I suppose they could be set to block each other but that seems like more work than necessary since just removing plt from portage seems like a better solution. The plt ebuild is for a very old version and has been obsoleted by the newer and maintained drscheme ebuild. At the very least, I think plt should be masked so someone doing "emerge -S drscheme" would be less likely to accidentally pick plt when they almost certainly want drscheme. I see that there is an mzscheme ebuild that also has conflicting files with drscheme. It is also a quite old 205 version and I think you can make the same case to remove that one from portage. However, since it really is a standalone package (albeit is a subset of drscheme) you _could_ argue for it to remain. However, I think it should either be updated or removed with my vote for removal since drscheme gives you all the functionality (and more) of mzscheme. At the very least, this old version should probably be masked. Reproducible: Always Steps to Reproduce: 1. emerge plt 2. scratch head and wonder why you got such an old version of drscheme 3. unmerge plt and emerge drscheme instead Thanks for listening! --Rob
dev-lisp/plt removed from portage.
