This issue is mostly resolved now. The current status of each components:
- seafile: the client syncing daemon. It installs seaf-daemon binary, libseafile library and a few header files. The library and headers are used by the GUI (seafile-client project).
- ccnet: ccnet daemon for the client. It installs ccnet binary, libccnet and ccnet header files.
- seafile-client: the client GUI. It relies on seafile and ccnet libraries and headers files.
- seafile-server: server core. It only installs seaf-server binary. No library or header files installed now. But it still installs python libraries.
- ccnet-server: ccnet-server daemon for the server. It installs ccnet-server binary, libccnet and ccnet header files. Python libraries are also installed.
So currently ccnet-server and ccnet still installs conflicting libraries and header files. But by now the libraries and headers are the same. In the future, only libraries and header files from ccnet-server project may be updated. So we suggest to use libraries and header files from ccnet-server project. Libraries and headers from ccnet-server will be compatible with the ccnet client.