trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: June 2015

Re: [trinity-devel] questions about rosegarden package

From: Fede Galland <federicogalland@...>
Date: Mon, 1 Jun 2015 21:17:45 -0300
On Tue, Jun 02, 2015 at 09:06:37AM +0900, Michele Calgaro wrote:
> -----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 :-)
> 

Alright, that answers all my questions for now! I'll take a look at the
git repo. I didn't know about the qt3-tqt3 converter.

Thanks a lot!