By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 571 - dbus-qt package names are unclear
Summary: dbus-qt package names are unclear
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tqtinterface (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other All
: P1 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks: 2969
  Show dependency tree / graph
 
Reported: 2011-10-30 12:33 CDT by Darrell
Modified: 2019-04-04 15:06 CDT (History)
4 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2011-10-30 12:33:52 CDT 
There are two packages named dbus-tqt. One is the original Qt3 bindings. The other is the backported bindings from Qt4.

How about less confusing names? Such as dbus-qt3-tqt and dbus-qt4-tqt or something similar?
Comment 1 Darrell 2013-04-15 13:05:01 CDT 
Tim, we're probably too far gone into this to change the package names at this point. How about we resolve this by providing clear package descriptions for each?

I don't know whether my original problem report is accurate. Proposed descriptions:

dbus-tqt:
---------

This package provides the TQt-based dbus bindings for applications using the Qt3 interface to D-BUS.

dbus-1-tqt:
-----------

This package provides the TQt-based dbus bindings for applications using the Qt4 interface to D-BUS.

Please edit!
Comment 2 Michele Calgaro 2018-07-28 03:05:49 CDT 
Perhaps package renaming is more appropiate. Also to check whether we need both packages or not.
Comment 3 deloptes 2019-04-04 15:06:23 CDT 
This reminds me my question from 1-2y ago when I was trying to understand why we have two of the kind

I would also vote for removing the one in favor of the other - of course I would prefer keeping the dbus-1-tqt, because I am working on it. But in general I ask my self why should we do that?

Finally when I run rdepends it shows that few things depend on libdbus-tqt-1-1c2

 apt-cache rdepends libdbus-tqt-1-1c2
libdbus-tqt-1-1c2
Reverse Depends:
  libdbus-tqt-1-1c2
  libdbus-tqt-1-dev
  libdbus-tqt-1-1c2-dbgsym
  libdbus-tqt-1-1c2
  amarok-engine-yauap-trinity
  kmplayer-base-trinity

and other few things depend on libdbus-1-tqt

$ apt-cache rdepends libdbus-1-tqt
libdbus-1-tqt
Reverse Depends:
  libdbus-1-tqt
  tdebluez
  libtdebluez
  libtdeobex
  tdepowersave-trinity
  tdelibs14-trinity
  libdbus-1-tqt-dev
  libdbus-1-tqt-dbgsym
  libdbus-1-tqt
  kdesktop-trinity

This is based only on my installation and I do not have many packages installed.

Perhaps when we finalize the work on dbus-1-tqt migration to this library will be much easier.