When updating a website on localhost with same name as project update lands in sites/project

Patch adds:

drush_pm_install_package()
- some verbose logging
- a drush_error when unsuccessful installing ... ie a full stop when installing multiple projects

drush_pm_update()
- verbose logging
- mkdir if check ... this was the start point for this bug

drush_pm_get_project_path()
- verbose logging
- fix for directory backtrace ... it was forward scanned instead of backwards.

(my setup is a little ruined ... so no patch)
The (offending) lines are in drush_pm_get_project_path

       $parts = explode('/', $path);
-      $i = count($parts) - 1;
-      $stop = array_search($project, $parts);
-      while ($i > $stop) {
-        unset($parts[$i]);
-        $i--;
+      while( $parts[ count($parts)-1] != $project){
+        array_pop( $parts);
       }

The bug is in calculating the $stop which finds the first occurance of $project where it should use (in my case) the last. Unless there are modules out there with their info files in directories like $project/$project/test.info

So I'm not sure whether this fix would not introduce a bug the other way around.

When having a site(s) setup like

- /var/www/annotate/sites/annotate/modules/annotate

the old algorithm would delete

- /var/www/annotate directory

and not the annotate module

- /var/www/annotate/sites/annotate/modules/annotate

which would be the usage scenario.

Could anybody be so kind to review this patch.

I know it's a weird problem having a website name the same as a module name but the code is 'so wrong' :p

And today I 'deleted' a local site again :-( drush pm update ubercart deleted my /var/www/ubercart/ site. It is fortunately a symlink.