Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Dependency check for language packs | ||
---|---|---|---|
Product: | Installation | Reporter: | Olaf Felka <olaf-openoffice> |
Component: | code | Assignee: | AOO issues mailing list <issues> |
Status: | CONFIRMED --- | QA Contact: | |
Severity: | Trivial | ||
Priority: | P2 | CC: | ingo.schmidt-rosbiegal, issues, kay.ramme, Mathias_Bauer, mdxonefour, santiago.bosio, stephan.bergmann.secondary |
Version: | OOo 2.0.4 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
Olaf Felka
2006-09-14 12:18:07 UTC
Accepted Not fixable in 2.1 time frame -> 2.2 It's about OOD languagepack on an OOC office. IS -> MBA: We have already talked about this. I do not see a realistic chance, to avoid this conflicts with the mechanisms of native installers. It seems to be more promising, if the Office checks at startup, which language packs are available and which of them can be used. This requires additional configuration settings in the language packs, that describe a versioning schema. I think 2.2 target is a bit optimistic on this. This happens when a new language pack has features that are not present in the installed Office version. Can this issue be solved by the new package restructuring? The package restructuring will change the content of the packages. But the problem of this task is not solved by the restructuring. We would need for every native installer mechanism a process, that keeps all packages consistent to each other. Office installation, patch installation, language pack installation, ... . I do not think, that the installer can guarantee this. *** Issue 86738 has been marked as a duplicate of this issue. *** 3.1 Reset assigne to the default "issues@openoffice.apache.org". |