ECM is "extra-cmake-modules", so probably a missing BDEP
MESSAGE is only for fairly important things relating to the port, and
should be kept really short. Duplicating info from the FAQ about sysctl
does not meet that bar for me.
However *not* including it in README and deferring to sysctl(8) manual
which says nothing about recording doesn't seem helpful - I'd mention the
actual sysctls in the README and say what happens if not set (e.g. "if you
only see blue video, make sure you have enabled the recording sysctls). Use
the URL for the FAQ page rather than "OpenBSD FAQ (Multimedia chapter)".
--
Sent from a phone, apologies for poor formatting.
On 15 July 2026 08:25:38 Pontus Stenetorp <[email protected]> wrote:
On Sat 11 Jul 2026, Daniil Ryvkin wrote:
On Fri, Jul 10, 2026 at 02:46:56PM -0500, izzy Meyer wrote:
> On Fri, 10 Jul 2026 06:20:23 +0300 Daniil Ryvkin <[email protected]> wrote:
> > On Thu, Jul 09, 2026 at 08:15:45PM -0500, izzy Meyer wrote:
> > > On Thu, 9 Jul 2026 20:50:00 +0300 Daniil Ryvkin <[email protected]> wrote:
> > >
> > > I had that sysctl set. I had a brain fart when reading your
> > > pkg-message. Perhaps this information in the pkg-message would be
> > > better in a pkg-readme for easy access after install, and perhaps
> > > other quirks that may be useful to the end-user?
> >
> > Thanks for the suggestion, moved the setup details to pkg-readme.
> > MESSAGE now only shows the essential sysctl commands.
>
> pkg-readme and pkg-message could be streamlined a bit.
>
> Additionally, it may be best just to point users to the multimedia FAQ
> as to not duplicate documentation in your pkg-readme. How this would be
> worded, should be up to you. But the idea is that end-users would have
> one central place for finding multimedia information not-specific to
> this port. Putting generic multimedia quirks about OpenBSD as a system,
> that are not specific to this port is redundant IMO.
>
> Same concept applies to the pkg-message. It is duplicate information
> from the FAQ multimedia page. But IMO *only* quirks specific to the
> obs-studio port should be in pkg-readme, everything else should point
> to the FAQ or the relevant manpage(s). No need to put in pkg-message
> notice to read the pkg-readme, pkg_add already informs the user that a
> pkg-readme was installed.
>
> Could you streamline pkg-readme and pkg-message?
Thanks, I missed the README template example. Moved setup details to
pkg-readme, MESSAGE now only shows the essential sysctl commands.
Generic multimedia info points to the FAQ and sndiod instead of
duplicating it.
Not that it matters much, but I thought I could test it on 7.9 -stable, but
it fails to build with:
CMake Error at cmake/linux/ecmconfig.cmake:5 (find_package):
Could not find a package configuration file provided by "ECM" with
any of
the following names:
ECMConfig.cmake
ecm-config.cmake
Add the installation prefix of "ECM" to CMAKE_PREFIX_PATH or set
"ECM_DIR"
to a directory containing one of the above files. If "ECM" provides a
separate development package or SDK, be sure it has been installed.
Call Stack (most recent call first):
cmake/linux/defaults.cmake:43 (include)
CMakeLists.txt:15 (include)
If I find the time, I will try it on a -current machine.
I am unsure if what is in pkg/README is worded in the best of ways though:
snd/0 Built-in audio device (microphone input).
snd/1 USB audio device, if present (microphone input).
snd/mon Monitor sub-device (desktop audio loopback, NOT a microphone).
snd/0 is not guaranteed to be a built-in audio device (I have boxes where
it is not), likewise snd/1 is not guaranteed to be a USB audio device, etc.
Is it not better just to defer to the manpages? None of this has to do with
OBS in particular, but is rather just how sndiod works.
