On Thu, Oct 02, 2014 at 09:33:54PM +0400, Kirill Bychkov wrote: > On Thu, October 2, 2014 12:41, Landry Breuil wrote: > > On Thu, Oct 02, 2014 at 10:40:16AM +0200, Landry Breuil wrote: > >> On Thu, Oct 02, 2014 at 11:54:33AM +0400, Kirill Bychkov wrote: > >> > We're living in an age of clouds, so I want to introduce port of a client > >> for > >> > "Next-generation Open Source Cloud Storage". > >> > http://seafile.com/en/home/ > >> > > >> > Currently only client is ported because server side is... well... not > >> > easy > >> in > >> > configuration and it's port is incomplete. > >> > > >> > Tested against Linux server and library with very big and tons of small > >> files. > >> > > >> > Comments? OK? > >> > > >> > P.S. You can find all the stuff in openbsd-wip. > >> > >> That mostly looks good to me, minor nits: > >> > >> - can you add comments to 'no-so-obvious-patches' ? like the removal of > >> evutil.h inclusion.. > >> - add a comment explaining why a test is disabled in libzdb.. > >> - seafile-admin references/hardcodes /var/seafile, while i dont see that > >> dir registered anywhere in a PLIST, nor with a corresponding user - is > >> that stuff supposed to be running as root ? > >> - i see a desktop client and a daemon - do i understand that 'both' are > >> needed for client functionality ? How does the daemon start ? > > > > oh and seafile-applet and ccnet manpages end up in main seafile package > > instead of the package where the corresponding binary is - is that > > normal ? > > > > Landry > > > - remove manuals belonging to another package. I'll report this upstream. > - add comments to some non ovious patches. i'm going to push them upstream. > - add comment about disabled test > - use mariadb by default and regen WANTLIB in libzdb > - remove unneeded patch for seafile-admin tool. we're not shipping server > part. > > New ports attached. Updated versions are also available in openbsd-wip.
All this reads good to me, i'll try to play with that in the coming months, but in the meantime i think it's ok to import it as-is and polish in-tree if there are runtime issues. Esp if you already tested it a lot... Landry
