February 17, 2024 1:56 AM, "Jan Beich" <jbe...@freebsd.org> wrote:
>> But the installed package reports: >> 8:09pm# pkg info --dependencies alsa-plugins >> alsa-plugins-1.2.7.1_3: >> alsa-lib-1.2.10_1 > > Check dependencies of subpackages instead e.g., > > $ pkg info -xd 'alsa-plugins-[^0-9]' > alsa-plugins-ffmpeg-1.2.7.1_3: > ffmpeg-6.1.1_3,1 > alsa-lib-1.2.10_1 > alsa-plugins-jack-1.2.7.1_3: > jackit-1.9.22_2 > alsa-lib-1.2.10_1 > alsa-plugins-pulseaudio-1.2.7.1_3: > pulseaudio-16.1_2 > alsa-lib-1.2.10_1 > alsa-plugins-samplerate-1.2.7.1_3: > libsamplerate-0.2.2_1 > alsa-lib-1.2.10_1 > alsa-plugins-speex-1.2.7.1_3: > speexdsp-1.2.1 > alsa-lib-1.2.10_1 > >> It appears to be missing the SUBPACKAGE dependencies. Is this >> intentional, or a bug? > > Intentional. See pkg-message: > > Plugins with extra dependencies moved into subpackages: > - alsa-plugins-ffmpeg > - alsa-plugins-jack > - alsa-plugins-pulseaudio > - alsa-plugins-samplerate > - alsa-plugins-speex In my opinion, that's _not_ correct. When we install any non-SUBPACKAGE package, anything listed in LIB_DEPENDS or USES are automatically listed as package dependencies. However, if I install audio/alsa-plugins, the only way I know what dependencies are required is to by consulting /usr/ports/audio/alsa-plugins/Makefile. And if audio/alsa-plugins was to be compiled with non-standard OPTIONS, it's impossible to tell what dependencies are _actually_ required. Cheers. -- Jonathan Chen <j...@chen.org.nz>
