Re: CVS commit: pkgsrc/net/yt-dlp

[Greg Troxel <gdt%lexort.com@localhost>]

Leonardo Taccari <leot%NetBSD.org@localhost> writes:

> Greg Troxel writes:
>> [...]
>> Stepping back and thinking about yt-dlp, the real question is: why does
>> this not depend on ffmpeg and a javascript engine?  As I see it
>> (fuzzily), our install, by upstream standards, is defective, because
>> things that are strongly recommended aren't depended on.  Once that's
>> fixed, the question of how to warn people is no longer important.
>> [...]
>> Would you object to just adding a ffmpeg8 dependency?   Do people want
>> to use yt-dlp without ffmpeg in significant number?
>
> Yes, I would object.
> Most extractors work without ffmpeg or other dependencies.
>
> I run yt-dlp on machines that only has python3* and it does
> its job. I would expect possible similar use cases.

If most usage doesn't need these, then they aren't properly strongly
recommended -- even if upstream wrongly describes them as strongly
recommended.

If they aren't strongly recommended, and are used only for unusual case,
and the man page sections that describe those unusual cases mentions
needing them, then all is ok and there's no need to suggest to anyone at
the broad level to install them.  In which case the last two lines of
DESCR can just be dropped (happy to do it if you agree).

I strongly believe that part of packaging is choosing the right
dependencies so that users get what they would want, if they understood,
especially for users that don't (or don't yet) understand.  Sometimes
that's not depending at all, sometimes that's a non-optional dependency,
and then there's default-on and default-off options.  I'm fine with
however you choose on ffmpeg dependencies.  What I don't think is ok is
the combination of choosing not to depend and then putting text in
MESSAGE that tells people that they really should manually install
ffmpeg.

It also seems that in an ideal world with infinite round tuits, that
someone(tm) should submit a bug report that upstream's strong
recommendations to install ffmpeg are incorrect.