Le mercredi 08 juin 2011 à 03:35 -0400, David Laban a écrit : > b) A good argument for why this (technical) restructuring of repositories is > actually better than the social thing of saying "This is the telepathy 6.0 > release. It contains tp-glib vX, tp-qt4 vY etc, and conforms to tp-spec vZ"? > (where X==Y==Z==6.0 is an optional identity) > > (stormer was grilling me today and I couldn't give him a good answer. If this > is actually the *wrong* solution, I should probably avoid wasting time trying > to (e.g.) drive CMake from autotools. I will put my efforts on hold for a few > days, so that we can have a discussion about this.)
I think this is like kernel modules: You can make your own external module but since internal API/ABI isn't guaranteed, you'll have an hard time to keep up with the latest API/ABI and will have to rebuild your external module for each kernel revision... So you're better in-tree. I'm wondering though, why don't we include CMs into the big telepathy tree, since they will suffer build issues each time we change spec and will need to be rebuild for each API/ABI change on the libtp-glib-dbus. Regards, Xavier Claessens. _______________________________________________ telepathy mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/telepathy
