roundcube at gmail.com
Mon Dec 5 17:58:28 CET 2011
On 03.12.2011, at 20:51, till wrote:
> On Fri, Dec 2, 2011 at 6:32 PM, A.L.E.C <alec at alec.pl> wrote:
> W dniu 02.12.2011 18:05, till wrote:
> > Never saw srcuri with PEAR packages:
> > http://pear.php.net/manual/en/guide.developers.package2.pecl.php
> > It looks like it's pecl related. What are you trying to achieve with it?
> As stated in my first post in this thread, for AGPL plugins we need to
> provide a link to source code.
> Reminds me to vote against the AGPL move.
The AGPL suggestion for Roundcube core has actually nothing to do with the requirement of making the source code of plugins available which are published under AGPL-
> So, we need some URL field in package.xml.
> Maybe I don't get it – but a pear package does not compile code. It's zipped up code in tar archive, compressed with gzip. The source is available. Can you explain why this link is necessary or who claims that it's necessary?
If you install a plugin which in licensed under AGPL you have to provide the source to the users of that system. That's required by the AGPL itself.
We (Roundcube) want to take the burden of collecting the links to all the AGPL sources away from the sysadmins which install Roundcube with AGPL plugins but collect them all in a single place. That's why we want the URL to the source of an AGPL plugin to be stated in the package itself. Of course we could also add some script which collects all the files directly from the Roundcube installation directory but this brings in some security topics which I'd like to avoid.
List info: http://lists.roundcube.net/dev/
More information about the Dev