> On Thursday 02 September 2010 02:04:05 Timothy Pearson wrote:
>> > Why you cannot use name kdelibs for your package?
>>
>> The official version in the archive of all KDE modules, e.g. kdelibs, is
>> the KDE4 version.  As Debian does not allow overrides by version
>> numbers,
>> there was no choice but to change the package names so as not to
>> conflict.
>>  Unlike SuSE, all official packages are in a single primary archive, so
>> the user cannot just deselect the KDE4 repository
>
> In SUSE also official packages are in the official repo. You cannot
> disable
> KDE4 repository without disabling the main release repo.
>
>> .  Besides, this method
>> allows KDE3 and KDE4 to live together should the user want to use both.
>
> We also have KDE3 and KDE4 excellently living together.
>
Then I may not understand enough about the RPM packaging system in use
under SuSE.  I can explain the technical details behind what is required
to have KDE3 and KDE4 work together, but it seems the main thrust of what
you are trying to do here is to promote OpenSUSE's KDE3 version over the
Trinity project.  Am I understanding you correctly?

I don't have time to argue over which implementation is better; there are
limitations in what I can do that are out of my control due to the Debian
package format and also the cooperativeness of the distribution
maintainers.  OpenSUSE has always been more supportive of KDE since the
beginning, however I am doing my best under Ubuntu and Debian within the
limits that I have.  The features that have been added from OpenSUSE are
not as numerous as those in the Trinity project (yes I did look at the
patch list), and they are generally built only for OpenSUSE.  Trinity
instead aims to provide packages for all distributions, as the old KDE
project once did.

Tim