--- Begin Message ---
|
Subject: |
Re: rclone license question |
|
Date: |
Wed, 28 Nov 2018 10:41:07 +0000 (40 minutes, 35 seconds ago) |
On 27/11/18 16:09, Michael Albinus wrote:
> my name is Michael Albinus, I'm one of the Emacs developers.
I'm a grateful emacs user - thank you for your work :-)
> These days
> I'm working on integration of rclone into Emacs Tramp, that means a user
> can access a remote file in the cloud from inside Emacs with the help of
> rclone.
Great :-)
> During my work, the question has been raised, how rclone accesses Google
> Drive (and the other cloud storages in general). The major point is,
> whether this access includes the download of whatever libraries from a
> cloud storage at runtime. This could raise license problems, and maybe
> violates Emacs term of use,
>
> For Google Drive, I understand that rclone uses the Google Go Standard
> App Environment, which is bundled with the rclone sources. No further
> library download needed at runtime, IIUC.
>
> Could you pls confirm this? And are there other cloud storages
> integrated in rclone, which would require a library download at runtime?
rclone is statically linked with all the libraries it needs and
doesn't download any code at runtime.
rclone itself is under an MIT licence. The libraries it uses are
under various Open Source licences and I haven't attempted to
catalogue them before!
I ran this tool (https://github.com/pmezard/licenses) over the source
-
I've attached the report
Cheers
Nick
--
Nick Craig-Wood <address@hidden> -- http://www.craig-wood.com/nick
[2. text/plain; rclone-licences.txt]...
--- End Message ---