Hello! Licensing has been resolved: https://github.com/haiwen/ccnet/issues/7 https://github.com/haiwen/seafile/issues/631 https://github.com/haiwen/seafile/issues/666
On Sat, Mar 17, 2018 at 06:13:03PM +0100, Georg Faerber wrote: > (Sorry for missing References and In-Reply-To.) > > Hi all, > > First of all: Thanks a lot for your work on seafile -- highly > appreciated! > > Upstream responded in the linked issue of Alexandre Rossi: > > "We're going to deprecate ccnet dependency in the upcoming 6.3 syncing > client. Ccnet is currently only used for syncing libraries created > before 3.0 servers. Because it uses TCP sockets to communicate with > seaf-daemon (the syncing daemon), it prevents users from running > multiple instances of syncing clients on Windows. So there would be no > ccnet in the client in the future. By the way, the drive client doesn't > rely on ccnet already." v6.3.2-server has been tagged in the upstream repo. > Therefore, once released, this > > > The very best solution of course would be if the two repos were merged > > again so that we can build ccnet and ccnet-server packages from the > > same source. > > seems possible then, doesn't it? Given that Debian has never distributed a Seafile 3.0 server, why not KISS, reduce the potentially greater attack surface, and just --disable-ccnet? If it has been officially depreciated upstream, then upstream should provide the option to do so. Cheers, Nicholas
signature.asc
Description: PGP signature
