Notices

Qole, I agree that it is a bit rough around the edges and not entirely robust. In fact it bails that often I've taken to running it in an infinite loop from a script, but it does actually perform its function. Reminds me of my first experiences with the Maemo RSS feed reader ;-)

Last night I ran a script on my server that just bounced DT-Talkie bundles back to my N800, and sure enough it receives them too. Early days though. With some debugging and GUI rework, I expect that it can become more acceptable.

Now, if only I can figure out how to rebuild it from source. I'm having some issues satisfying the dependencies in scratchbox, not the least as it has a need for a package called dtn-api, which I've never heard of and assume is some derivative of the fuller dtn package. Clearly its a build-time dependency only, as I don't have it installed on my N800 (I have the full dtn package I built installed there).

BTW, you can hack out existing contacts in the txt files in /media/mmc1/.dttalkie and restart dttalkie.

Personally I'd like to thank palash_cse for pitching up here and being responsive to the problem I mentioned with my DTN2 build. I hope (s)he isn't too put off by initial feedback here.

Basically I created dtn-api.pc file locally so that the dtn2 api library path can be configured using pkgconfig tool while building the dttalkie project. But it doesn't make the project making process generic. In the latest updates, you can configure the project with --with-dtn parameter, which takes value of the top dtn2 installation directory.

For example: ./configure --with-dtn=/home/foobar/dtn-2.6.0

So, no hassle of dtn-api dependency anymore.