trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: June 2015

Re: [trinity-devel] questions about rosegarden package

From: Michele Calgaro <michele.calgaro@...>
Date: Tue, 02 Jun 2015 09:06:37 +0900
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 06/02/2015 02:35 AM, Fede Galland wrote:
> hi all, I'm a newcomer to trinity, so I might be using the wrong channel for my question.
> 
Hi Fede, welcome to TDE!

> First of all, let me state that I had grown dissapointed by the trend current linux is going, but I installed the
> trinity repos just to have the old rosegarden easily installed on my wheezy systems and I just can't believe how
> lightweight and featureful TDE is. It seems to perform better than the good old KDE3.5
Sure it is, since TDE forked from KDE3.5 and fixed and improved several things over time :-)

> 
> To the point:
> 
> Is anybody mantaining the rosegarden version shipping in trinity's repos?
It is maintained in the same way other packages are, i.e. we try to make sure the package builds and install over time.

> I mean, is it expected to report stability bugs on it?
If you mean "someone is adding patches/fixes from outside", the answer is most likely "no", but if you wish to
contribute to that you are welcome. You can suggest required patches or even trying adding them yourself at first. Any
good patch can then be pushed to the source repo.

> 
> Why did you ship with version 1.7.0 instead of the latest 1.7.x series, 1.7.3 (as per rosegarden's sourceforge)?
Not sure, probably at the time TDE was forked, 1.7.0 was the version in the KDE repo and then no one worked on that.
You can file an enhancement bug report to TDE bugszilla, possibly pointing to a location where to download 1.7.3. Or
again feel free to contribute yourself.

> 
> I tried compiling Rosegarden 1.7.3 just to see if it was easily achievable, but I got only as far as to point cmake
> to the tqt3 libs. It fails searching for KDE3's kcfg and whatnot. If this indeed is the correct channel I will
> provide debugging info. In a somewhat unrelated topic: Is it still possible to build KDE3.5 minded applications on
> trinity? Is there a guide with steps to change the dependencies? In other words, is trinity backwards compatible
> with KDE3.5?
Yes and no. TDE is not backward compatible with KDE3.5 as is, since many things have been renamed to avoid conflicts
with KDE and because an intermediate layer (tqinterface) was added between qt/tqt and TDE apps.
But an old KDE3.5 app can be converted to a TDE application and rebuilt. See the scripts in the experimental/kde-tde
folder in the git repo. As a quick guide:
1) import the KDE code
2) convert qt to tqt (see experimental/qt3-tqt3/convert_existing_qt3_app_to_tqt3)
3) convert kde code to tde (see experimental/kde-tde)
4) import the admin and cmake code from the main repo
5) build and hunts for errors :-)

> 
> One other app I'd like to have running is kmiditracker, which depends heavily on KDE3.5.
> 
> [rantmode] Thanks for holding this little fortress in the free software world. Many a great code base gets lost
> everytime someone decides we should be switching to a completely different as soon as something becomes stable
> enough not to worry about it (as it's happening to KDE4 right now). [/rantomde]
> 
> Have a good one!
> 
> Fede
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCgAGBQJVbPONAAoJECp1t8qK3tXPB1IQAJAShuyv9nVNHyvKLU6oFnRD
aTPDlZvqK7Eb6wMKDHAbnOkHsMLdahKogToDVK7yIUwWARZlMGGkAXUVPwK5Z1KH
w1nlynnrxCjdy3g+s2GVkKHL7TaT8pql5i59IvKKTQJMZxd+zzG/Zuwc0xvqb69M
1/ylg95BbGtiiiCKIYo4vTlYaOW9a5CJ+GgyWP+0oy8kQ5z3I0Dz1AGVd3hg1hiV
Nf8o9BQM0ILd+Fik5AMq82vCsaMcTdmBRLcmVSLCNQrcnxxqd7I98Zene2er/GUl
Wda+9UeBkfoW42QMeyZlyr4LQvRQjONyLA9e3z9r/LffzRIRgpX85cTktNznRAwg
a/8AH3L5bVBfY3DmKc2r6ZLJm80gOUvn4CE95NKAgREPRegm9D7NyZLQlxjiVuSu
pxidZ6/obvu4l3lvJr3o+v9chMgKxVsNpIqepCkj5KOxuzF5fMPUwKvt4sERJYkS
RscpOpfRGFs/CW80qg1Gr6a2SYJoBUbbCG8Zu6VDyAltseKwepIqiGxQc3K37KlR
UIGwiDK4FOpKvHuWJSNv5vXsRSd3HP8saC0lpLGOKvJFhFJTNCfV/NvA0TCDogDk
hAbPIbK6JAVWSiyRpLtbLNI9BJXP0EVfCE5XzG6XixMVakMcDsf5LKJz4wE04eEv
an1NmWKytBS4f22Wf1lc
=WKcA
-----END PGP SIGNATURE-----