Community Packages

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#76710 - [obs-studio] package is built using github tarballs; project developers advise against that

Attached to Project: Community Packages
Opened by Jérôme Petazzoni (jpetazzo) - Thursday, 01 December 2022, 18:29 GMT
Task Type General Gripe
Category Packages
Status Assigned
Assigned To Jonathan Steel (jsteel)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 3
Private No



At the moment, the obs-studio package is built from source obtained by fetching github archive tarballs:

However, the OBS project developers advise to *not* use that, and to use git instead:

As a result, the obs-studio package 28 on Linux is missing websocket support (see  FS#76069 ), because websocket support comes from a git submodule that doesn't get included in the github archive tarballs.

I don't know what's the proper etiquette here:

* on the Archlinux side, we say "please include all source code in git archives"
* on the OBS side, they say "You can assume OBS does not distribute tarballs and it is incumbent on packagers to use git. There is no way to disable github's broken tarballs or we would have."

What do?
This task depends upon

Comment by Jonathan Steel (jsteel) - Thursday, 01 December 2022, 20:31 GMT
I'll jot down a few thoughts:

* They provide the source tarball, so it was natural to use it.
* They don't have to use github; publish a (complete) tarball on their website.
* Aside from this websocket feature what else is missing? obs-browser will not be included as it requires a dated version of cef-minimal from my understanding.
Comment by Thomas Bocek (tom_draft) - Saturday, 03 December 2022, 20:14 GMT
Looks like there is a fix than could be merged soon:
Comment by Thomas Bocek (tom_draft) - Sunday, 12 February 2023, 20:07 GMT
As a temporary workaround, I'm using the following here: