Please join RPM Fusion project

[kwizart]

Hi there,

I've seen that you provide packages for fedora and EL for displaylink adapters.
Please consider joining the rpmfusion.org project to provide theses packages there.

There will be a need to adapt the package to handle the kmod mechanism which will allow to provide pre-built kernel modules.

See also https://rpmfusion.org/Contributors

[ssaavedra]

It's an interesting proposal. We are not currently providing EL releases, though; CentOS 7 is built but I'm not sure if it works.

As it currently is, this project does not totally comply with the Fedora Packaging Guidelines. For example, three packages should be generated: one for the evdi dkms sources, another one for the evdi library, and a separate one for the displaylink binaries themselves.

While this would make it easier in terms of installing each thing separately (and in terms of which license applies to which binaries), it puts a burden on version maintenance. The current "single package" generation is more appropriate for downloading the RPM and installing it, but is a stopper for introducing it into a proper DNF repository.

We cannot upload this on a COPR repository, though, since parts of the redistributed files are under a proprietary non-opensource license (the DisplayLink binaries).

Another issue would be switching from dkms to kmod, which is also an interesting task by itself.

If this is something that has enough popular attention, I can start a "proper-dnf" or "rpmfusion" branch in order to address these changes while we still support the current course of action until this is finished.

👍 the issue if you are interested in that :)

[kwizart]

Thx for the answer.

Having a separate branch seems appropriate.

[ssaavedra]

I have just created a fedora-guidelines branch to adapt the specfile so that it fits the packaging guidelines, including separate packages for {a,}kmod-evdi and displaylink-lib.

[ffgiff]

@kwizart I've put in a PR (#97) for building as an akmod. Would you mind giving some feedback on whether this would be right for RPMFusion? In particular, I've only done two packages, one for akmod and one for all the userland stuff, but this thread suggests it would be preferable to do three, akmod, libevdi and displaylink binaries.

[kwizart]

@ffgiff
This looks like a good start, thx for looking into this.
I would suggest to have evdi-kmod.spec and displaylink.spec (the later having a "virtual" Provides: evdi-kmod-common to satisfy the suer

Also please have a look on https://rpmfusion.org/Contributors
You will have to provide both a spec file and src.rpm to review (one for each package in a separate bugzilla entry, so we will use our own tooling to process the review).

Thx

[genebean]

Just curious how this work shook out.

[kd5678]

Yes I would like to know also, because I need it.. Its for me hard to understand that the hardware in the year of 2021 not have drivers for linux/fedora... Because everything in the internet is running on linux its NOT windows...

[firefoxlover]

I see its still not part of RPMFusion which is kinda sad. Awesome that this project is still going! Thanks a lot!

[firefoxlover]

In the meantime, this COPR should work

https://copr.fedorainfracloud.org/coprs/crashdummy/Displaylink/

[rapgro]

I see its still not part of RPMFusion which is kinda sad. Awesome that this project is still going! Thanks a lot!

As RPMFusion is an official repository there's some process to review package to get imported. Maybe I can offer some help with https://rpmfusion.org/Contributors .

[nathan-weinberg]

I am not a Fedora contributor/maintainer and I see that the https://github.com/displaylink-rpm/displaylink-rpm/tree/fedora-guidelines branch is basically abandoned, but if there is any interest from the project maintainers in trying to get this into the Fedora project I'm happy to try and facilitate a connection to start that process