https://bugs.documentfoundation.org/show_bug.cgi?id=158781

Stéphane Guillou (stragu) <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.documentfounda
                   |                            |tion.org/show_bug.cgi?id=36
                   |                            |019
                 CC|                            |heiko.tietze@documentfounda
                   |                            |tion.org,
                   |                            |stephane.guillou@libreoffic
                   |                            |e.org
     Ever confirmed|0                           |1
             Blocks|                            |120063
             Status|UNCONFIRMED                 |NEEDINFO

--- Comment #2 from Stéphane Guillou (stragu) 
<[email protected]> ---
(In reply to Gabor Kelemen (allotropia) from comment #0)
> 6. Go to the command line, try running from the installation directory the 
> instdir/program/unopkg add foo.oxt 
> command (or unopkg.com on Windows), where the foo.oxt is what you downloaded
> in the first point.
> -> the extension is installed. This is inconsistent with the intention of
> setting these config keys set in step 4.
Reproduced.

> 8. Use 
> instdir/program/unopkg remove $identifier
> to remove the just installed extension
> -> this also succeeds, which is also inconsistent with step 4.
Reproduced.

(In reply to Stephan Bergmann from comment #1)
> ...and note that issue 36019 had deliberately left unopkg functionality
> unchanged (for better or worse; just saying)
Thanks for pointing that out, Muhammet bug 36019 comment 16 says it was by
design:

(In reply to Muhammet Kara from bug 36019 comment #16)
> (In reply to Heiko Tietze from bug 36019 comment #14)
> > Sounds good. But don't forget the unopkg command-line option to add,
> > validate, remove, reinstall, and list extensions.
> 
> As this feature is for use of advanced users (or admins), disabling the
> unopkg commands seems unnecessary since it can be enabled/disabled via the
> expert configurations. Moreover, advanced users (or admins) might want to be
> able to add/remove extensions while preventing the regular users from
> installing/removing extensions.
Gabor and Heiko, what do you think?


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=120063
[Bug 120063] [META] Options dialog's expert configuration bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to