This was last reviewed a couple of years ago in bug 1089340. Checking the current situation of the package and recent changes to the codebase would be a good idea at the occasion of the path move.