Issue 120350 - Extensions included in the basis core package are always installed by default
Summary: Extensions included in the basis core package are always installed by default
Status: CONFIRMED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: 4.1.4-dev
Hardware: All Linux, all
: P3 Normal with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2012-07-23 15:44 UTC by jolatt
Modified: 2017-09-26 14:52 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description jolatt 2012-07-23 15:44:41 UTC
Extensions which belonges to AOO per default are in package ooobasis3.4-core01_3.4.0-1_amd64.deb. They were installed in the user directory at the first start of AOO.

I prefer installing selected extensions for all users. Therefore I had to delete the extensions in .../share/extensions/install before first start of AOO or deinstalling them via Extensionmanager and then install my extensions.

IMHO it would be better to integrate the extensions as single DEBs or in one DEB in the installation package of AOO and not in the
ooobasis3.4-core01_3.4.0-1_amd64.deb.
Comment 1 jolatt 2012-08-13 07:55:25 UTC
(In reply to comment #0)
> Extensions which belonges to AOO per default are in package
> ooobasis3.4-core01_3.4.0-1_amd64.deb. They were installed in the user
> directory at the first start of AOO.

Installation of these extensions happens without confirmation!

> I prefer installing selected extensions for all users. Therefore I had to
> delete the extensions in .../share/extensions/install before first start of
> AOO or deinstalling them via Extensionmanager and then install my extensions.
> 
> IMHO it would be better to integrate the extensions as single DEBs or in one
> DEB in the installation package of AOO and not in the
> ooobasis3.4-core01_3.4.0-1_amd64.deb.

Or the user should be asked, whether the extensions should be installed or not.
Comment 2 jolatt 2012-08-13 07:55:25 UTC
(In reply to comment #0)
> Extensions which belonges to AOO per default are in package
> ooobasis3.4-core01_3.4.0-1_amd64.deb. They were installed in the user
> directory at the first start of AOO.

Installation of these extensions happens without confirmation!

> I prefer installing selected extensions for all users. Therefore I had to
> delete the extensions in .../share/extensions/install before first start of
> AOO or deinstalling them via Extensionmanager and then install my extensions.
> 
> IMHO it would be better to integrate the extensions as single DEBs or in one
> DEB in the installation package of AOO and not in the
> ooobasis3.4-core01_3.4.0-1_amd64.deb.

Or the user should be asked, wether the extensions should be installed or not.
Comment 3 jolatt 2013-07-21 15:08:34 UTC
Same in AOO 4.0.0 RC
Comment 4 Ariel Constenla-Haile 2013-07-21 19:57:20 UTC
Confirming
Changing issue type to DEFECT
Setting keyword REGRESSION

There is still a regression in the way dictionary extensions are included since Apache OpenOffice: 

In Sun/Oracle era, the dictionaries were not bundled extensions, but packages by their own; they were in their own rpm/deb package and you could choose whether to install it or not.

From a Linux user perspective, this is a regression, and you are forced to install the bundled dictionaries with the basis core-01 package.

In AOO 4.0.0 there are no more pre-registered extensions (Presenter Screen and Presentation Minimizer), so the bug is reduced in 4.0.0 to only bundled extensions.

Adapting the summary: Extensions included in the basis core package are always installed by default

Each extension should be in their own rpm/deb package (although Sun/Oracle didn't include the other extensions - MediaWiki, Report Builder, Presenter Screen, Presentation Minimizer, PDF Import - in their installation sets, dictionaries were included each on a single package).
Comment 5 jolatt 2014-02-04 18:44:21 UTC
It can't be hard to change this (for me) annoying bug.
Comment 6 Oliver-Rainer Wittmann 2014-03-19 14:06:20 UTC
(In reply to jolatt from comment #5)
> It can't be hard to change this (for me) annoying bug.

great. Do you have a patch at hand which I can apply?
Comment 7 jolatt 2014-03-19 16:06:53 UTC
Sorry, but I'm not a programmer.
Comment 8 Oliver-Rainer Wittmann 2014-03-20 07:55:24 UTC
(In reply to jolatt from comment #7)
> Sorry, but I'm not a programmer.

Oh, sorry. I misunderstood your statement that 'it would not be hard for you to change this'
Comment 9 jolatt 2015-10-18 17:53:24 UTC
Not fixed!
Comment 10 jolatt 2017-02-22 07:44:18 UTC
The build Apache_OpenOffice_4.1.4_Linux_x86-64_install-deb_en-US_2017-02-21_12:44:59_1783882.tar.gz still has the dict-en-20170101.oxt included in the package openoffice-core01_4.1.4-1_amd64.deb.

See comment 4. 

Provide extensions in a separate package, please.
Comment 11 jolatt 2017-03-11 15:02:53 UTC
Apache_OpenOffice_4.2.0_Linux_x86-64_install-deb_en-US_2017-02-27_04:15:06_1784492.tar.gz

See Comment 10!
Comment 12 Andrea Pescetti 2017-03-11 16:05:13 UTC
The answer to the specific comment (i.e., dev builds do not contain the latest English dictionary) is simply that we usually update all dictionaries shortly before release.

But is you can compute an MD5 sum you can write a patch for this: it's enough to modify extensions.lst. The file was already updated in recent days anyway and it now includes the latest version, see http://svn.apache.org/viewvc/openoffice/trunk/main/extensions.lst?r1=1781403&r2=1784925&diff_format=h

This of course leaves open the original request (i.e., packaging dictionaries in own DEB or RPM files for easier installation).
Comment 13 jolatt 2017-03-12 07:10:01 UTC
(In reply to Andrea Pescetti from comment #12)

> This of course leaves open the original request (i.e., packaging
> dictionaries in own DEB or RPM files for easier installation).

That's it.
Comment 14 jolatt 2017-07-13 06:28:29 UTC
Target Milestone?
Comment 15 oooforum (fr) 2017-07-22 15:57:14 UTC
(In reply to jolatt from comment #14)
> Target Milestone?
To do it, a developer must submit a patch.
Comment 16 jolatt 2017-09-26 14:52:21 UTC
(In reply to oooforum (fr) from comment #15)
> (In reply to jolatt from comment #14)
> > Target Milestone?
> To do it, a developer must submit a patch.

That's right. But is that so heavy, to do it?

If yes, you should remove these extensions and making up an information on the download page, where to find and how to install these extensions,