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

SSL-enabled w3c-libwww conflicting with GPLd programs



Hello,

in the course of preparing packages for the new w3c-libwww release, I
planned to compile the w3c-libwww package with SSL support, and to
file a bug for the removal of w3c-libwww-ssl.

However, AIUI because the OpenSSL license and the GPL are not
compatible, this would mean that GPLd packages could no longer use
libwww and at the same time remain in full compliance with the
licenses.

Currently, glibwww (GPL) depends on libwww, and a large number of
packages "use" it through libwww-perl - not sure whether that can be
called "linking".

So, should I keep maintaining both SSL and non-SSL versions of
w3c-libwww?

Cheers,

  Richard

-- 
  __   _
  |_) /|  Richard Atterer     |  CS student at the Technische  |  GnuPG key:
  | \/¯|  http://atterer.net  |  Universität München, Germany  |  0x888354F7
  ¯ '` ¯


-- 
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: