brew is also miles away from what it used to be. They have recently changed their philosophy about building from source and software support compiled into their built bottles. Did you know that neither mpv or mplayer bottles ship with libdvdread support?
Building mplayer from source fails due to an error building libavcodec against x264. For some reason, the x264 version is not being correctly picked up in the Homebrew build process so it is trying to use a deprecated x264 API that has been built, which is causing it to fail however building the same software outside of Homebrew (same source tarball that Homebrew downloaded) builds just fine with libdvdread and x264 in ffmpeg support.
I'd report it further but the time last someone asked about it they were basically told to fuck off. Their rules for avoiding burnout state the following which really summarizes their recent change in policy:
> 1. Use Homebrew
>Maintainers of Homebrew should be using it regularly[...]
>3. Prioritise Maintainers Over Users
>It's important to be user-focused but ultimately, as long as you follow #1 above, Homebrew's minimum number of users will be the number of maintainers. However, if Homebrew has no maintainers it will quickly become useless to all users and the project will die. As a result, no user complaint, behaviour or need takes priority over the burnout of maintainers. If users do not like the direction of the project, the easiest way to influence it is to make significant, high-quality code contributions and become a maintainer.
Yet proposing a patch for this gets met with "create your own tap and stop bothering us". I'd love to help you, guys, if you weren't gigantic pricks about it!
Their formula does not disable libdvdread support, but their build from source process fails to detect it if it is otherwise installed. A build from the vanilla source tarball picks it up just fine. So this is not a "Homebrew decided to disable this option", it seems to be a "Homebrew's build process actively avoids searching for other installed software even when the authors of that underlying software enable support by default".
brew is also miles away from what it used to be. They have recently changed their philosophy about building from source and software support compiled into their built bottles. Did you know that neither mpv or mplayer bottles ship with libdvdread support?
Building mplayer from source fails due to an error building libavcodec against x264. For some reason, the x264 version is not being correctly picked up in the Homebrew build process so it is trying to use a deprecated x264 API that has been built, which is causing it to fail however building the same software outside of Homebrew (same source tarball that Homebrew downloaded) builds just fine with libdvdread and x264 in ffmpeg support.
I'd report it further but the time last someone asked about it they were basically told to fuck off. Their rules for avoiding burnout state the following which really summarizes their recent change in policy:
> 1. Use Homebrew
>Maintainers of Homebrew should be using it regularly[...]
>3. Prioritise Maintainers Over Users
>It's important to be user-focused but ultimately, as long as you follow #1 above, Homebrew's minimum number of users will be the number of maintainers. However, if Homebrew has no maintainers it will quickly become useless to all users and the project will die. As a result, no user complaint, behaviour or need takes priority over the burnout of maintainers. If users do not like the direction of the project, the easiest way to influence it is to make significant, high-quality code contributions and become a maintainer.
Yet proposing a patch for this gets met with "create your own tap and stop bothering us". I'd love to help you, guys, if you weren't gigantic pricks about it!