Package Details: obs-ndi 4.9.1-2

Git Clone URL: https://aur.archlinux.org/obs-ndi.git (read-only, click to copy)
Package Base: obs-ndi
Description: Network A/V in OBS Studio with NewTek's NDI technology
Upstream URL: https://github.com/Palakis/obs-ndi
Licenses: GPL2
Conflicts: obs-ndi-bin, obs-ndi-git
Provides: obs-ndi
Submitter: emileet
Maintainer: emileet
Last Packager: emileet
Votes: 6
Popularity: 1.09
First Submitted: 2020-04-19 03:06
Last Updated: 2020-10-05 14:33

Latest Comments

celilo commented on 2020-05-16 00:56

Thanks for the info. I added another comment at ndi-sdk requesting the change.

emileet commented on 2020-05-16 00:50

@celilo agreed, several requests were put forward to the maintainer however it appears they fell on deaf ears

celilo commented on 2020-05-16 00:32

Thanks, I can now compile both ndi-sdk and obs-ndi without manually modifying the PKGBUILDs. I still believe, per my comment in ShayBox's build that we should simply communicate with other package maintainers and have the ndi-sdk maintainer add a versioned provides, such as "provides=('libndi=4.9.1')". In doing so, the user installing any of the packages will know if manual intervention is required and can notify the maintainer of the issue.

Currently Shaybox's build prevents installing two completely compatible programs, and this build allows a small possibility of breaking another package if compatibility is broken.

emileet commented on 2020-05-07 12:11

@Fresco thank you for the suggestion, i believe upstream is already aware of the issue https://github.com/obsproject/obs-studio/issues/2625

Freso commented on 2020-05-07 11:29

Re: 1: I’m not sure what you mean, ShayBox? The "obs-ndi-4.9.0.tar.gz" file is an archive of the plugin’s sources, not a binary build of the module. This is perfectly as it should be.

Re: 2: Agreed, but until ndi-sdk provides libndi, no reason to make a change here.

Re: 3: Have you considered filing an issue at https://bugs.archlinux.org/ (or maybe it’s an upstream issue?) emileet? Seems like something other OBS plugins would need to compile too, and it is a bit heavy to download the complete OBS source code when what is needed should already be available. However, it is not an issue with this package as-is, but an issue that needs fixing either in the Arch Linux package and/or with upstream.

emileet commented on 2020-05-07 05:35

@ShayBox the reason for the binary sources is to verify the integrity of the source files with makepkg, although unnecessary i find it to be good practice. i'm happy to just checkout releases instead if you prefer but i prefer this way as it's a continuity of how upstream obs-studio is built.

your concern of ndi-sdk is valid in the event ndi-sdk updates so i will make the adjustments when obs-ndi is updated, the original reason for this choice was to consider users who may require the header files from ndi-sdk.

the reason why we're sourcing obs-studio is due to the fact that building the plugin requires the "obs-frontend-api.h" header which isn't provided by the obs-studio package (pacman -Ql obs-studio | grep frontend).

ShayBox commented on 2020-05-07 03:18

This package should be compiling from tagged sources, not sourcing from tagged binary sources.
It should be depending on libndi not ndi-sdk, one is a shared package group, the other is a single package.
And it should also not be pulling obs-studio, this is a plugin, you don't need to install obs.