Bug#920437: ITP: displaylink -- Proprietary driver for DisplayLink devices

2019-01-25 Thread Ben Hutchings
On Fri, 2019-01-25 at 14:21 -0500, Hanno Stock wrote:
> Am Fr, 25. Jan 2019, um 17:03, schrieb Ben Hutchings:
> > Please consider choosing a more specific package name.  Since we
> > have
> > free drivers for some DisplayLink devices, we should encourage
> > users to
> > use those where possible.
> 
> Ok, I see. What about displaylink-nonfree ? One could also append to
> the long description a hint which package to
> use for devices supported by the free drivers.

That seems sensible.

Ben.

-- 
Ben Hutchings
I'm not a reverse psychological virus.
Please don't copy me into your signature.




signature.asc
Description: This is a digitally signed message part


Bug#920437: ITP: displaylink -- Proprietary driver for DisplayLink devices

2019-01-25 Thread Hanno Stock
Am Fr, 25. Jan 2019, um 17:03, schrieb Ben Hutchings:
> Please consider choosing a more specific package name.  Since we have
> free drivers for some DisplayLink devices, we should encourage users to
> use those where possible.

Ok, I see. What about displaylink-nonfree ? One could also append to the long 
description a hint which package to
use for devices supported by the free drivers.



Bug#920437: ITP: displaylink -- Proprietary driver for DisplayLink devices

2019-01-25 Thread Ben Hutchings
On Fri, 2019-01-25 at 14:22 +0100, Hanno Stock wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Hanno Stock 
> 
> * Package name: displaylink
>   Version : 4.4
>   Upstream Author : DisplayLink (UK) Ltd.
> * URL : https://www.displaylink.com/downloads
> * License : proprietary
>   Programming Lang: binary
>   Description : Proprietary driver for DisplayLink devices
> 
> This is the proprietary binary component of the driver for DisplayLink
> devices. It communicates via libusb with the DisplayLink device and uses
> the opensource evdi kernel module for presenting a virtual graphics
> device to the system.
[...]

Please consider choosing a more specific package name.  Since we have
free drivers for some DisplayLink devices, we should encourage users to
use those where possible.

Ben.

-- 
Ben Hutchings
Always try to do things in chronological order;
it's less confusing that way.




signature.asc
Description: This is a digitally signed message part


Bug#920437: ITP: displaylink -- Proprietary driver for DisplayLink devices

2019-01-25 Thread Hanno Stock
Package: wnpp
Severity: wishlist
Owner: Hanno Stock 

* Package name: displaylink
  Version : 4.4
  Upstream Author : DisplayLink (UK) Ltd.
* URL : https://www.displaylink.com/downloads
* License : proprietary
  Programming Lang: binary
  Description : Proprietary driver for DisplayLink devices

This is the proprietary binary component of the driver for DisplayLink
devices. It communicates via libusb with the DisplayLink device and uses
the opensource evdi kernel module for presenting a virtual graphics
device to the system.

-

DisplayLink devices are for example USB based docking stations and
USB-attachable secondary screens. Unfortunately newer DisplayLink devices
are not supported by libdlo, an open source driver for older DisplayLink
devices. 

However DisplayLink provides an Ubuntu installer for their newer drivers
and allows repackaging the binary components for other distributions.
According to a DisplayLink employee: "The text of the license was written
to ensure the driver can be repacked by other distros and redistribute.
As long as the text of license file is replicated, and binaries are
redistributed as provided in the .run package (unmodified), and it is
still possible to identify what component is what and where it came from,
the license terms are met IMO." [1]

In order for Debian to support DisplayLink devices it would make sense
to package this driver for the non-free component.

[1] https://www.displaylink.org/forum/showthread.php?t=64854=license