summaryrefslogtreecommitdiff
path: root/cui/source/tabpages
diff options
context:
space:
mode:
authorStephan Bergmann <sbergman@redhat.com>2013-02-07 15:37:57 +0100
committerStephan Bergmann <sbergman@redhat.com>2013-02-07 15:42:39 +0100
commit57955e1961181ffe7e77c23da7fb73db5d545f4c (patch)
treeebc8c4f075700d5590089d0dc8fb2e303e047b6c /cui/source/tabpages
parentf3e42e07da568553b7e2c056259a2667d6789ca3 (diff)
Revert "Cleanly remove an extension again that cannot be activated while installing it"
This reverts commit 3c71fa1e5ee6cd83f713c65a372006bc3aef0953. There are cases (like failure to install a per-user extension during upgrade), where the user may want to still see the broken extension in the Extension Manager, instead of it "disappearing completely." A better fix would be to roll back registration of the broken extension completely, so that "unopkg list" would not list the first half of its parts as "is registered: yes" and the second half as "is registered: no."
Diffstat (limited to 'cui/source/tabpages')
0 files changed, 0 insertions, 0 deletions