Message: previous - next
Month: June 2012

Re: [trinity-devel] TQt3 Name Change - Potential Problem - what about apps that Need moc?

From: "David C. Rankin" <drankinatty@...>
Date: Wed, 20 Jun 2012 13:31:01 -0500
On 06/20/2012 12:53 PM, Darrell Anderson wrote:
> Which package? I grepped the entire source tree and found no such configure option:
> grep -rn "enable-pinentry-qt" .
> So which package do you add that configure option?
> Darrell

Yikes Darrell,

  It is not a TDE package.. Sorry, it is one of the system dependencies for
gpg/gpg-agent. The package name is 'pinentry'. I'm sure it is on your box as we
speak. That is what brought up my concern. "Will this renaming break all
packages that are NOT tde packages but that rely on Qt?"

  If I understand your earlier response, the qmake paths/properties will handle
outside packages that look for the Qt executables and find them under their new
names. I don't know how that works, but I guess there is a pkgconfig type lookup
or config file that would do it. Where I'm still lost is if there is both Qt4
and TQt3 installed and some package looks for the old Qt name -- how is it
prevented from grabbing the Qt4 provided package by mistake?

  pinentry was just the example I stumbled across today. In the (tde-world,
non-tde-world), it is the non-tde-world apps that concerned me regarding the
name change.  May not be an issue, but all the work you are having to do in the
'tde-world' having to be duplicated for all 'non-tde-world' Qt packages was what
scared me :)

David C. Rankin, J.D.,P.E.