On Wed, Jun 13, 2018 at 02:30:18AM +0200, Adam Borowski wrote: > > anbox-modules-dkms - Android kernel driver (binder, ashmem) in DKMS format > > Could you please explain (here and/or in the package's description) reasons > why an user would prefer this version of the modules over what's in mainline > kernel trees? > This upstream repo in out-of-tree format can be built against various kernel versions. I think upstream creates this repo because many distributions(including most Debian based) don't enable these modules in their kernel. Since this repo already exists, then packaging it is more convenient to enable these modules in kernel(and waiting other Debian derivatives to sync up, not sure if they just sync with Debian or have own kernel config). I don't have good sentence for package description. Suggestions are welcome. > Also, you have GPL-3 scripts managing GPL-2 modules, this is borderline and > I'm not quite sure of which side of the border. > the debian/ directory is split from previous anbox package, which is in GPL-3. Since all things in debian/ dir are written by myself, it's easy to change the license. But I don't think it would be problem. Just to clarify, there's no d/patches file, so no GPL-3 code is patched to GPL-2 code. -- Regards, Shengjing Zhu
Attachment:
signature.asc
Description: PGP signature