trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: January 2014

Re: [trinity-devel] tdebinding (libsmoketqt) conflicts with libtqt-perl (libsmoketqt) - which is correct?

From: Slávek Banko <slavek.banko@...>
Date: Wed, 29 Jan 2014 01:40:20 +0100
On Tuesday 28 of January 2014 21:56:56 David C. Rankin wrote:
> A lot!, that's why we are renaming the 'trinity-devel' list to the
> 'darrell-anderson' list...
>
> � Now on to the more pressing matter -- how to control:
>
> if libsmoke from A, then
> � no libsmoke from B
> elif libsmoke from B, then
> � no libsmoke from A
> fi
>
> � Is this purely a packaging matter, of should there be some TDE logic that
> does this in the autotool/automake setup.
>
> � Right now libtqt-perl is a prime example of the hell we will find
> ourselves in when automake 2 arrives. It does not build with automake 1.14
> without significant hacks. Slavek has taken an initial patch of the problem
> and created an update to libtqt-perl and it looks like he has set libsmoke
> to build only in tdebinding. See:

I understand that in libtqt-perl is a "copy" of kalyptus and smoke from the 
tdebindings. In fact, as a "third-party" for cases that are not yet available 
in the system. As you can see, this copy not been updated to reflect changes 
in tdebindings. Update kalyptus been addressed until now, when the problem 
occurred.

I would venture to say that the "right place" for libtqt-perl would include it 
as another part of tdebindings.

Slavek
--