Re: Using libunrar in KArchive?

--===============4240296575614448455==
Content-Type: multipart/signed; boundary="nextPart4043306.nYoxxsPCsq";
	micalg=pgp-sha1; protocol="application/pgp-signature"

--nextPart4043306.nYoxxsPCsq
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"

On Thursday 27 March 2014 13:51:48 David Faure wrote:
> On Thursday 27 March 2014 12:36:52 Sune Vuorela wrote:
> > On 2014-03-27, David Faure <[email protected]> wrote:
> > > Do you think it would be possibly to make karchive optionally
> > > depend on libunrar, for *extracting* rar files (with no support
> > > for creating rar files)?
> > > 
> > > The license for libunrar has limitations, but AFAICS only "do not
> > > recreate the compression algorithm", so if we don't do that,
> > > would it be a problem?
> > 
> > It would be code that none of the big distributions would ship, so
> > I'm not sure it would be that ... useful.
> 
> OK. Since I will write this code anyway (a customer needs it), this
> only leaves one question - is it ok to put it in karchive anyway?

What do you mean by "put it in karchive"? As the cited Fedora page says 
the license is GPL-incompatible. You cannot link GPL code together with 
any parts of unrar's source code. Calling the unrar executable from 
karchive should be okay though.

Leaving those technical details aside, the unrar license does not meet 
the requirements of our licensing policy 
(http://techbase.kde.org/Policies/Licensing_Policy). Consequently, I 
don't see how we can allow it in our repositories.


> As
> you say the distros will not provide the optional dependency so it
> won't be compiled, but having the code in there in the first place
> isn't a problem, right?

Au contraire. IMHO putting it in any of our repositories is a huge 
problem. If we allow this code in our repositories then we set a 
precedent for allowing any source code with non-free licenses in our 
repositories.


> The alternative is to host the code elsewhere (playground, github...)
> but that makes it harder (I might need access to karchive_p.h).

I don't see an alternative to hosting it outside of KDE's repositories.


Regards,
Ingo

--nextPart4043306.nYoxxsPCsq
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEABECAAYFAlM1xbIACgkQGnR+RTDgudjJIQCeJggtCfwxX71HP7nmQ9ltfk8d
Rc0AoOLOjO93v60KqVZhgU51tLBxdMa+
=n8Lr
-----END PGP SIGNATURE-----

--nextPart4043306.nYoxxsPCsq--

--===============4240296575614448455==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-licensing mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-licensing

--===============4240296575614448455==--