[Telepathy] Telepathy 1.0 will never happen
Simon McVittie
simon.mcvittie at collabora.co.uk
Wed Jun 8 02:52:44 PDT 2011
On Wed, 08 Jun 2011 at 03:35:31 -0400, David Laban wrote:
> a) Your perfect-world directory structure for telepathy-core if we decide to
> go that way.
For each library, if users are meant to #include <foo/bar.h> then the library
should live in either /foo or /somewhere/foo in its tarball and git repo.
I'd personally put them at top level, to avoid having seemingly-redundant
paths like telepathy-glib/telepathy-glib/account.c.
(Rationale: then you can -I${abs_top_srcdir} -I${abs_top_builddir} (possibly
with /somewhere appended) and use an installed or uninstalled copy, without
noticing any difference, via #include <foo/bar.h>.)
Beyond that, whatever. I'd personally go for something like this (imagining
Gabble and a Wocky submodule to be part of the One Big Module, for the sake
of argument):
${top_srcdir}
\- configure.ac (top level)
\- doc/
\- glib/
\- qt4/
\- examples/
\- glib/
\- qt4/
\- gabble/
\- mission-control/
\- mission-control-plugins/
\- m4/
\- spec/
\- Account.xml (etc.)
\- telepathy-farstream/
\- telepathy-glib/
\- TelepathyQt4/
\- Farstream/
\- tests/
\- lib
\- gabble
\- presence (etc.)
\- glib
\- qt4
\- mc
\- account-manager
\- dispatcher
\- tools/
\- wocky/
\- configure.ac (for submodule)
\- wocky/
\- wocky-util.h (etc.)
Regards,
S
More information about the telepathy
mailing list