Hello again, I've just uploaded working versions of the Seafile Client packages (that are libsearpc, seafile and seafile-client) that don't require ccnet anymore.
So if anyone wants to continue with packaging ccnet with the ccnet-server sources, please feel free to do so. Best regards, Moritz On 17.03.18 18:13, 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." > > 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? > > Cheers, > Georg > -- Moritz Schlarb Unix-Gruppe | Systembetreuung Zentrum für Datenverarbeitung Johannes Gutenberg-Universität Mainz Raum 01-331 - Tel. +49 6131 39-29441 OpenPGP Fingerprint: DF01 2247 BFC6 5501 AFF2 8445 0C24 B841 C7DD BAAF
<<attachment: schlarbm.vcf>>
signature.asc
Description: OpenPGP digital signature
