**** BEGIN LOGGING AT Sun Jul 01 02:59:58 2012
Jul 01 12:50:18 <guyzmo> heyall
Jul 01 12:50:55 <guyzmo> is there some documentation to be read about oe and angstrom dbus/connman implementation ?
Jul 01 12:54:03 <bluelightning> gui
Jul 01 12:54:05 <bluelightning> er
Jul 01 12:54:19 <bluelightning> guyzmo: I would say just look at the upstream documentation for those projects
Jul 01 12:54:30 <bluelightning> there's nothing special about how it's used within angstrom
Jul 01 12:54:59 <guyzmo> bluelightning - well, actually there is
Jul 01 12:55:29 <guyzmo> it does not respect the API documented in moblin's documentation
Jul 01 12:55:34 <guyzmo> (the dbus API)
Jul 01 12:56:16 <guyzmo> and the name has been changed (though this is minor, and I agree that the dbus path net.moblin is more explicit than org.moblin.connman )
Jul 01 13:59:47 <bluelightning> guyzmo: that documentation is ancient
Jul 01 14:00:20 <bluelightning> guyzmo: the up-to-date documentation can be found together with the upstream connman source at connman.net
Jul 01 14:23:22 <guyzmo> bluelightning - that's that documentation I'm refering about, I even tried out some examples from moblin's connman upstream, and things are somehow different
Jul 01 14:24:00 <guyzmo> for example, the test-connman script delivered with angstrom is a really reduced version of moblin's
Jul 01 14:24:14 <guyzmo> and I tried to hack a passphrase setting script, with no success
Jul 01 14:24:36 <guyzmo> most of the properties described in the moblin's documentation are not existent
Jul 01 14:33:10 <bluelightning> guyzmo: what I'm telling you is, the moblin documentation is out of date
Jul 01 14:33:53 <bluelightning> angstrom builds recent versions of connman from http://connman.net/
Jul 01 14:51:09 <guyzmo> damn, I misread
Jul 01 14:51:11 * guyzmo is getting tired
Jul 01 14:51:21 <guyzmo> (well, working on sundays doesn't help )
Jul 01 14:51:41 <guyzmo> interesting to see outdated version has more features than up-to-date
Jul 01 15:01:21 <bluelightning> I'm not convinced that that's the case... it could be that the test script has been gutted though, not sure
**** ENDING LOGGING AT Mon Jul 02 02:59:58 2012