Magento Connect Should Not Report Extensions are Installed if they're Not Installed

[astorm]

Current versions of the Magento Connect Package Management system will report that a package has been successfully installed even if Magento Connect was unable to install the package due to file permission errors.

Steps to Reproduce

1. Find a Magento Connect package file that installs files to app/code/community
2. Change file permissions on app/code/community such that the web server cannot write to app/code/community (i.e. chmod 755 app/code/community)
3. Log into Magento Connect
4. Click "Choose File"
5. Browse to the Magento Connect package file and select it
6. Click the "Upload" button

Expected Behavior

• Magento Connect reports it was unable to install the package due to file permission errors

Actual Behavior

• Magento Connect reports it was able to install the package and adds it to the list of packages
• Package is not actually installed on system

A screencast demoing this problem has been uploaded to YouTube here

http://www.youtube.com/watch?v=TmRxTTmGyN0

[magento-team]

I reported it to our bugtracker however submitting a fix with code and test would highly increase the chance of such issues being fixed in Magento core.

[astorm]

This fix requires feedback from product/leads on the best direction to take, and probably requires architecture changes to Magento connect itself to accommodate the fix. I get wanting to encourage contributions, but a generic copy/paste "fix with code and test" comes off as tone-deaf here.

[magento-team]

Hello Alan, we expect major changes to happen in the connect itself so let's leave this one for now as a bug report.