Add binary blob driver to Factory

Hi folks, I hope everything goes well. I would like to add a DisplayLink driver to the Factory repository. This driver is split into: * An open source part: https://github.com/DisplayLink/evdi * A private part: a binary blob I've been able to package it and make it work. I've already added the open source part to Factory. My question is if I can add the binary part although it's a private binary. Also, what license should be the right one in this case? Here is the (private part) package at obs: https://build.opensuse.org/package/show/home:jtorres:displaylink/displaylink.... Here is the license that comes when extracting the private part: https://paste.opensuse.org/pastes/12fa620d3e13 Thank you. Joan.

On 01. 02. 24, 13:20, Joan Torres via openSUSE Factory wrote:
Hi folks, I hope everything goes well.
I would like to add a DisplayLink driver to the Factory repository. This driver is split into: * An open source part: https://github.com/DisplayLink/evdi * A private part: a binary blob
I've been able to package it and make it work. I've already added the open source part to Factory.
My question is if I can add the binary part although it's a private binary. Also, what license should be the right one in this case?
It very much depends on the license (and I assume Ciaran would decide once submitted, or ask him directly). We distribute some firmware in kernel-firmware. Some is even binary blob and we use SUSE-firmware for that purpose (whatever it means). OTOH, some cannot be distributed (like b43legacy or rtl8761b) and has to live outside build.opensuse.org completely. Like on packman. -- js suse labs

Please use legal@suse.de for any inquiries, Ciaran works for Benz nowadays. Please be aware of our NonOSS/NonFree repository. https://en.opensuse.org/Package_repositories#Non-OSS In the case of Leap we do double check with legal on such pieces as part of the IPRQ process. https://progress.opensuse.org/issues/131879 Lubos On Thu, Feb 1, 2024 at 3:39 PM Jiri Slaby <jslaby@suse.cz> wrote:
On 01. 02. 24, 13:20, Joan Torres via openSUSE Factory wrote:
Hi folks, I hope everything goes well.
I would like to add a DisplayLink driver to the Factory repository. This driver is split into: * An open source part: https://github.com/DisplayLink/evdi * A private part: a binary blob
I've been able to package it and make it work. I've already added the open source part to Factory.
My question is if I can add the binary part although it's a private binary. Also, what license should be the right one in this case?
It very much depends on the license (and I assume Ciaran would decide once submitted, or ask him directly).
We distribute some firmware in kernel-firmware. Some is even binary blob and we use SUSE-firmware for that purpose (whatever it means).
OTOH, some cannot be distributed (like b43legacy or rtl8761b) and has to live outside build.opensuse.org completely. Like on packman.
-- js suse labs
-- Best regards Luboš Kocman openSUSE Leap Release Manager

Thanks for your answer. Regarding NonOSS repo: From obs Factory, how a package ends at OSS or NonOSS repo?

There are dedicated projects for such packages. You just need to submit it there. https://build.opensuse.org/project/show/openSUSE:Leap:15.6:NonFree https://build.opensuse.org/project/show/openSUSE:Factory:NonFree On Fri, Feb 2, 2024 at 12:36 PM Joan Torres via openSUSE Factory <factory@lists.opensuse.org> wrote:
Thanks for your answer.
Regarding NonOSS repo: From obs Factory, how a package ends at OSS or NonOSS repo?
-- Best regards Luboš Kocman openSUSE Leap Release Manager

Hi, Still, packages in there need a valid redistribution license verified by legal. Ciao, Marcus On Fri, Feb 02, 2024 at 12:47:07PM +0100, Lubos Kocman via openSUSE Factory wrote:
There are dedicated projects for such packages. You just need to submit it there.
https://build.opensuse.org/project/show/openSUSE:Leap:15.6:NonFree https://build.opensuse.org/project/show/openSUSE:Factory:NonFree
On Fri, Feb 2, 2024 at 12:36 PM Joan Torres via openSUSE Factory <factory@lists.opensuse.org> wrote:
Thanks for your answer.
Regarding NonOSS repo: From obs Factory, how a package ends at OSS or NonOSS repo?
--
Best regards
Luboš Kocman openSUSE Leap Release Manager
-- Marcus Meissner (he/him), Distinguished Engineer / Senior Project Manager Security SUSE Software Solutions Germany GmbH, Frankenstrasse 146, 90461 Nuernberg, Germany GF: Ivo Totev, Andrew McDonald, Werner Knoblich, HRB 36809, AG Nuernberg

On Feb 02 2024, Lubos Kocman via openSUSE Factory wrote:
There are dedicated projects for such packages. You just need to submit it there.
https://build.opensuse.org/project/show/openSUSE:Leap:15.6:NonFree https://build.opensuse.org/project/show/openSUSE:Factory:NonFree
For Factory, it is still to be submitted to its devel project. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different."
participants (5)
-
Andreas Schwab
-
Jiri Slaby
-
Joan Torres
-
Lubos Kocman
-
Marcus Meissner