[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Packaging owncloud-client



Hey,

Very interesting - i'm using and programming some moths now for owncloud-
client and use it, but I never thought about a good short description for it.

> Meanwhile I've just discovered "http://en.opensuse.org/Mirall";.  Is
> this the same software?  This description presents it as basically an
> installer for ownCloud, which is an aspect completely missing from
> your description.  What's going on here?

Yes it is the same software. Funny I never discovered that featuere (and 
actually the devs doesn't told so too :)

> Wait... reading the description for libowncloudsync0, I don't see why
> you're mentioning CSync here if mirall doesn't use it.  The fact that
> libowncloudsync0 derives historically from something called CSync may
> be something to mention in the description for libowncloudsync0, but I
> don't see why it's relevant here for people trying to understand what
> mirall does and whether they want to install it.

Currently the plugins of CSync are important to be able to use the protocols. 
libowncloudsync0 is only a very small layer to make it easier to use CSync. 
(libowncloudsync make directory checking, stores credentials ); CSync only 
syncs the directories and exitis afterwards (like rsync).

> (What do the dependencies look like here - some sort of "Recommends: 
libocsync-plugin-all | libocsync-plugin-sftp | ..."?)

Yup will be. In this moment, I have not added recommends, but as longer I'm 
thinking about it, I would add them to recommends or suggests.

> > SMB, SFTP or to a cloud storage named ownCloud. Actually you need the
> 
> If it's *via* SMB or *via* SFTP or *to* the cloud, you can't just
> elide the second "via".  You could say "it supports synchronizing via
> SMB/SFTP or to cloud storage"...
> 
> But is "SMB" still accepted as a name for the protocol?  I thought
> they deprecated the name in the mid-nineties (in favour of CIFS) and
> the v1 protocol in the mid-noughties (in favour of SMB2).

mmh good point - I only took the name from the source :)

> Saying that you can synch via these protocols or to ownCloud just
> makes me wonder what protocol it uses to synch to ownCloud and whether
> it's possible to use SFTP instead.

ownCloud uses webDAV but with special featueres. I'll ask, i any webdav store 
will be useable with owncloud-client/mirall.

> "Presumably" was me saying that *I* didn't know - I was assuming you
> would be able to correct it!  Is this how it works?  Do I nominate a
> set of other machines to synch with, or does each of those machines
> need to have mirall configured with the same synching group name, or
> what?  I would guess they don't all need to be running Linux and
> mirall, given that it supports SMB, but then does that mean I only
> need mirall installed on the machine I configure the folders and
> computers from?

I never test syncing via SMB/SFTP but I think it's a clear server/client 
structure. You have to define one folder to sync to - And if every machine use 
the same folder to sync to you have a set of computers with the same files.
Mirall/owncloud-client runs on linux,windows and Mac. An CLI is alos available 
named pyOwncloud (debian name python-owncloud; available in sid).

> And I left this phrased as something that sounds more like a bug than
> a feature.  Why do I want it to sometimes decide to leave some target
> devices out?  It sounds as if it will leave out synching with your
> home NAS while you aren't at home; but will it synch with your home PC
> while you're away?  And if it's willing to do that, why not then synch
> from your home PC to the NAS?

If you are not at home, you need a router and IPAddress that supports 
connectiong to your NAS from outside.

> 
> Besides, "https://github.com/dmacvicar/mirall"; (if *that's* the same
> mirall) says "Network location awareness not implemented yet".

If I understood Klass the right way, these featueres come from the CSync and 
is implemented now: See http://doc.owncloud.org/desktop/1.2/architecture.html

My suggestions:
 
Package: mirall
Description: folder synchronization across a set of computers - GUI
The ownCloudSync system lets you always have your latest files wherever
you are. Just specify one or more folders on the local machine and a server to 
synchronize to. You can configure more computers to synchronize to the same 
server and any change to the files on one computer will silently and reliably 
flow across to every other.
.
mirall provides the graphical client for ownCloudSync, which supports
synchronizing within a network via CIFS/SFTP or using cloud storage provided 
by ownCloud (if appropriate libocsync-plugin-* packages for the specific 
protocol are installed). The recommended client for ownCloud is named 
owncloud-client.

Package: owncloud-client
Description:  folder synchronization with an ownCloud Server - GUI
The ownCloudSync system lets you always have your latest files wherever
you are. Just specify one or more folders on the local machine to and a server 
to synchronize to. You can configure more computers to synchronize to the same 
server and any change to the files on one computer will silently and reliably 
flow across to every other.
.
owncloud-client provides the graphical client specialising in
synchronizing with cloud storage provided by ownCloud. An alternative
client named mirall is available that can also use CIFS/SFTP.

Package: libowncloudsync0
Description: folder synchronization for mirall and ownCloud Client - libraries
The ownCloudSync system lets you always have your latest files wherever
you are. Just specify one or more folders on the local machine to and a server 
to synchronize to. You can configure more computers to synchronize to the same 
server and any change to the files on one computer will silently and reliably 
flow across to every other.
.
This library is based on CSync, but adds functions that are missing in
CSync and more specific to graphical clients.

Regards,

sandro

Attachment: signature.asc
Description: This is a digitally signed message part.


Reply to: