Re: Using libunrar in KArchive?

--===============0951507116793352800==
Content-Type: multipart/signed; boundary="nextPart13433602.urqhy9DEd2";
	micalg=pgp-sha1; protocol="application/pgp-signature"

--nextPart13433602.urqhy9DEd2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-15"

On Saturday 29 March 2014 10:33:10 David Faure wrote:
> On Saturday 29 March 2014 10:31:03 Albert Astals Cid wrote:
> > El Divendres, 28 de mar=E7 de 2014, a les 19:45:07, Alex Merry va=20=

escriure:
> > > On 28/03/14 18:55, Ingo Kl=F6cker wrote:
> > > > 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 optionall=
y
> > > >>>> depend on libunrar, for *extracting* rar files (with no
> > > >>>> support
> > > >>>> for creating rar files)?
> > > >>>>=20
> > > >>>> The license for libunrar has limitations, but AFAICS only "d=
o
> > > >>>> not
> > > >>>> recreate the compression algorithm", so if we don't do that,=

> > > >>>> would it be a problem?
> > > >>>=20
> > > >>> It would be code that none of the big distributions would
> > > >>> ship, so
> > > >>> I'm not sure it would be that ... useful.
> > > >>=20
> > > >> 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?
> > > >=20
> > > > 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.
> > >=20
> > > I would assume this is putting the code that *uses* libunrar in
> > > KArchive, which is fine.  Obviously, putting libunrar itself in
> > > would
> > > not be.
> >=20
> > Yep, that is what i understood too.
>=20
> And it is what I meant, too.
>
> The code in karchive itself would be LGPL just like the rest of
> karchive. It would just have a dependency on libunrar - and get
> disabled if libunrar isn't available.

Okay. Then I see no licensing problem with putting this code in our=20
repositories.


Regards,
Ingo

--nextPart13433602.urqhy9DEd2
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)

iEYEABECAAYFAlM3JUAACgkQGnR+RTDgudi7ZgCfe1uVEjrs1Hv/xiS/zl60gDtJ
RnQAn3l+77c3imouymQYraTzio4h42Fc
=0cGl
-----END PGP SIGNATURE-----

--nextPart13433602.urqhy9DEd2--

--===============0951507116793352800==
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

--===============0951507116793352800==--