It seems that the Emby server has changed license from GPL-2 to "proprietary core with open-source components":
https://github.com/MediaBrowser/Emby/issues/3479#issuecomment-444985456
As such, it seems that the sources for the 3.6 version and onward won't be distributed. I'm not sure what needs to be done here, but since I haven't seen a discussion about it yet, I'm opening a new issue.
Thanks!
Here is a discussion about Emby forks and alternatives:
https://github.com/nvllsvm/emby-unlocked/issues/28
And here is what looks to me as an active fork (but don't quote me on that):
Emby wasn't built from sources in nixpkgs anyway. So I think the first step would be to change the license to unfree with the 3.6 update.
If a fork gains traction I think it makes sense to package it.
Jellyfin seems to gain traction, maybe we could package it ?
After a few try it will not be trivial to package it as it is a dotnet core app and there seems to be no generic builder for that purpose.
This might be useful: https://blog.lextudio.com/offline-publishing-asp-net-core-apps-cf22f45158af
There still need a way to fetch package from Nuget in a local repo
And Emby 4 is out which is closed source now
Now that Jellyfin is packaged and has a module, I think it's safe to close this issue ^^
Most helpful comment
Jellyfin seems to gain traction, maybe we could package it ?
After a few try it will not be trivial to package it as it is a dotnet core app and there seems to be no generic builder for that purpose.
This might be useful: https://blog.lextudio.com/offline-publishing-asp-net-core-apps-cf22f45158af
There still need a way to fetch package from Nuget in a local repo
And Emby 4 is out which is closed source now