I propose the following enhancements to crossdev: * The uninstall function be modified to clean up more crap. For instance, if I have manually unmerged the toolchain packages, there is still a lot of litter left behind, but the uninstall function will fail after attempting to unmerge them and not continue to clean the rest of what crossdev leaves behind. (high importance) * Add a --list type of option to list the toolchains crossdev has generated/is managing. Maybe this just requires doing a cat /etc/portage/categories? (medium importance) * Add a --validate option (requires target) to validate a particular toolchain is properly installed (just validate all of the things are present that uninstall would remove) (lower importance)
crossdev seems to clean my toolchains just fine. you need to provide details, not vague "lot of litter". crossdev doesnt "manage" packages. it merely calls emerge on ebuilds. if you want to see what *packages* are installed, then use normal package utilities like `qlist -I cross-`. same goes for validation. ebuilds themselves make sure things are installed properly, not crossdev.
> crossdev seems to clean my toolchains just fine. emerge -C cross-foo/binutils cross-foo/gcc at least leaves -gcov and -cpp executables.
dont `emerge -C` stuff. use `crossdev -C`.
