20 Jan
2014
20 Jan
'14
10:30 p.m.
On Monday 20 of January 2014 23:04:04 Timothy Pearson
wrote:
For me it does not sound very nice. This would cut off the network support
for
all users who have knetworkmanager functional at this time.
OK. I guess we need to fix knetworkmanager8 then.
On Monday
20 of January 2014 22:29:31 Timothy Pearson wrote:
tdenetworkmanager
> At the beginning - one unnecessary -
knetworkmanager8. This being
> replaced by
> tdenetworkmanager, no longer being updated and may be removed from
> nightly-builds.
tdenetworkmanager only works on NM 0.9 and above. The older software
(knetworkmanager8) is needed for NM 0.8 and below.
Aha, I did not know this. I thought that tdenetworkmanager uses
tdehw-library,
not directly network-manager. Therefore, I assumed that is
not dependent on the version of network-manager => that dependency is
addressed in tdehw-library.
And I didn't consider it necessary to include NM <= 0.8 support in the
tdehw library. ;-)
Otherwise, we have a problem, because the commit
a111d47e9 in
dbus-1-tqt
causes FTBFS in knetworkmanager8!
Ah, OK. I am tempted to just say TDE R14 supports NM 0.9 and above, and
kill off knetworkmanager8 completely. Thoughts?
By the way, tdenetworkmanager is built successfully on
all currently
supported
Debianu / Ubuntu distributions.
It will build, but the DBUS calls will fail at runtime (the user will be
informed properly, but there is no way to make it work). Yet another
reason I really hate DBUS sometimes!