Message: previous - next
Month: June 2013

Re: [trinity-users] coming soon

From: "Timothy Pearson" <kb9vqf@...>
Date: Mon, 10 Jun 2013 02:18:15 -0500
> Le 09/06/2013 19:22, Slávek Banko a écrit :
>> On Sunday 09 of June 2013 19:07:56 Jan Stolarek wrote:
>>> That's great news! Can we expect new packages to appear (other than the
>>> ones mentioned in the link)? I'm being a bit selfish here, but for me
>>> lack of kbibtex in trinity is a blocker and a reason not to upgrade to
>>> Debian 7.0 from an ancient Suse distribution.
>> Yes, I will not forget your request to KBibTeX. However, before the
>> integration package to the stable branch I first need to prepare it for
>> inclusion in the official GIT tree => prepare for the master branch R14.
>> And with this I will deal after release v3.5.13.2.
>> Please a little patience.
>> Slavek
> Slavek, I already manage to build kbibtex (and other applications)
> against / QT3.
> To achieve that, I had to write some patches to avoid FTBFS. I can post
> the patches in bugtracker.
> So, people, do not forget to create a bug for each packaging request so
> that I can post patches.
> The thing I'm currently lacking is an easy way to convert QT3=>TQT3 in
> the application source code, so that we can import in the GIT repository.
> Francois

You can try using the automated conversion script here:

Be warned that it takes a LOT of CPU time to run, and that the result
probably won't compile the first time around.  However, it will deal with
99% of the tedious renaming without intervention.

You then need to take into account the more recent TDE header file and
class name changes.  Unfortunately, I do not have a script to
automatically convert a project to use the new TDE class names and header
files, so you would need to make those changes by hand or via your own

How I typically handle import of a new application is I first commit the
last known working version of the application from the original source
(i.e. the original project website) to a new GIT repository.  I then apply
and commit all changes needed to get it building on Qt3 with TDE 3.5.13.x,
then finally run the autoconversion tools and commit the first working
version for TDE R14.  This keeps the original versions around in the GIT
history in case something broke during build fixes and/or R14 conversion
and is not noticed until far in the future (this has happened many times