Issue 79838 - unopkg --log-file logs "disabling" instead of "removing" an extension
Summary: unopkg --log-file logs "disabling" instead of "removing" an extension
Status: ACCEPTED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: current
Hardware: All All
: P4 Trivial (vote)
Target Milestone: AOO Later
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-20 14:33 UTC by joerg.skottke
Modified: 2013-02-07 22:04 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description joerg.skottke 2007-07-20 14:33:02 UTC 
When an extension removal is logged the log states that the extension has been
"disabled" which is a bad wording as the option to disable already exists within
the Extension Manager. The correct term must be "removed" to be consistent with
the online help.
Comment 1 joachim.lingner 2007-08-16 15:09:24 UTC 
Technically "disabling" is correct because the files will only be removed when
the Extension Manager is started the next time after a restart of OOo or unopkg.
Therefore "Removing" is not correct either.

Maybe adding a note like the following would do:

"The files will be removed the next time the Extension Manager will be run from
OOo after OOo has been restarted ......"

That is, they will not be removed right now, but later.
Comment 2 joachim.lingner 2007-08-16 15:12:52 UTC 
JL->BH: What do you think? Could you provide a string?
Comment 3 bettina.haberer 2007-09-06 16:24:07 UTC 
I suggest the string "The extension will be removed after restarting OOo."
Comment 4 joachim.lingner 2007-09-07 11:47:16 UTC 
retarget to OOo later