trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: January 2014

Re: [trinity-devel] Missing packages in nightly-builds, renaming one git submodule

From: Slávek Banko <slavek.banko@...>
Date: Mon, 20 Jan 2014 23:14:35 +0100
On Monday 20 of January 2014 23:04:04 Timothy Pearson wrote:
> > On Monday 20 of January 2014 22:29:31 Timothy Pearson wrote:
> >> > 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 tdenetworkmanager
> > 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?
>

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.

> > 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!
>

Please, you have an overview of the differences between dbus calls for 
network-manager 8 and 9?

> Tim
>

Slavek
--