Re: Fwd: Re: Calligra translations are enabled

On 15 December 2010 13:07, Cornelius Schumacher <[email protected]> wrote:
> On Wednesday 15 December 2010 Boudewijn Rempt wrote:
>> On Tuesday 14 December 2010, Chusslove Illich wrote:
>> > [1] For the two inheritors of ex KOffice to be both installable on the
>> > same system, they must not have PO files with common names between
>> > themselves. I realize that there are likely many other similar conflicts
>> > that will have to be resolved in the following months, just mentioning
>> > this one for the record.
>>
>> Both suites will not be co-installable. The library names, plugin names and
>> so on won't change, nor will the resources, headers and so on be renamed.
>
> I think we need a better solution here. All KDE applications should be co-
> installable without conflicts.

There're more problem than just application names and plugins.
For example, the question is which application opens files for, say,
ODT mimetype?
We have no simple one-click solution for typical user.

Disclaimer: I am writing this not to state anything against further
development of "Group A" koffice.

I believe many users would see installing calligra 2.4 as upgrade from
koffice 2.3.
Thus setting recommendation for uninstallation of koffice before
installation of calligra would be benefcial for most of the users.
When we agree on having conflicting packages, users at least will be
aware that the apps won't coexist properly.

Moreover, as we have seen in the (fine) reaction to my SQLite
deployment entry [1], some distros probably have their policies and it
is hard to claim they will be shipping koffice 2.4 (if it's release)
and calligra 2.4 in the default repositories.

There's also a question if the desire "All KDE applications should be
co-installable without conflicts." is realistic and if this is the
purpose of KDE Project, which is not about deployment but about
delivery of the software in source code form (except for KDE on
Windows and partially KDE on Mac, no idea about Solaris now). I am
asking this because I think there's no realistic solution if we add
"3rd party KDE apps" to the set of "KDE apps". Moreover, nobody can
block development of a fork of any app within the KDE infrastructure,
even conflicting each other.
I think once the sitution clears up, one of {Calligra|KOffice-A}
suites will be practically more like 3rd-party than the other. Is this
an issue at all? Isn't it a task for distros to resolve?

[1] http://www.kdedevelopers.org/node/4156

-- 
regards / pozdrawiam, Jaroslaw Staniek
 http://www.linkedin.com/in/jstaniek
 Kexi & Calligra (kexi-project.org, identi.ca/kexi, calligra-suite.org)
 KDE Software Development Platform on MS Windows (windows.kde.org)
_______________________________________________
koffice-devel mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/koffice-devel