8 Jul
2011
8 Jul
'11
2:32 p.m.
Ilya, the fact is that by causality/coincidence the project trinity
and some rpm windows-like distributions use the same "prefix" (/opt
/opt/kde3 in redhat or suse), and therefore, by any
causality/coincidence have a match/compatibility, but trinity never
was compatible with applications preinstalled or precompiled unless
rebuild against trinity desktop/libs.
On Fri, Jul 8, 2011 at 4:44 AM, Ilya Chernykh <anixxsus(a)gmail.com> wrote:
On Thursday 07 July 2011 22:10:53 Timothy Pearson
wrote:
--
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com
Cofundador de Venenux; debian based multimedia alike free only
zealots users (oh well, i try but..too many free guidelines buahhh)
http://shutendouji.net
creador de massenkoh linux; debian enhanchements for better up to date
support on stable brand, including non-free soft.
* The extent of the renaming for the 3.5.13
release would be core
libraries and non-user-visible strings. This would be done only to make
downstream packaging easier (i.e. rename libkdecore.so to libtdecore.so,
etc.).
Sorry, but what the purpose in renaming the library files?
This will break the binary compatibility and also dependencies on rpm-based systems.
I would like to see Trinity and old KDE3 applications as much compatible as possible
so one can choose either trinity's or kde3's core and have his old apps still
working.
For this reason we have even KDE3 in KDE:KDE3 repository building against a
Trinity-patched
Qt3 so that the both could use the same Qt3 package.
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messsages on the Web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting