Re: [homebrew] LibAV conflicts with FFmpeg - thoughts?
- From:
- Max Howell
- Date:
- 2011-10-25 @ 09:06
We're overdue a conflicts field.
IMO we should install it keg-only. And then provide instructions for
how to brew unlink ffmpeg and brew link libav.
Obviously this is only done for formula that have the conflicts_with DSL.
Ideally deps would then install_name_tool link with the keg path
instead of the HOMEBREW_PREFIX, but upgrades don't work with that kind
of thing yet, so it will have to wait.
On 24 Oct 2011, at 16:22, Misty De Meo <mistydemeo@gmail.com> wrote:
> We've had a request or two to add a formula for LibAV, a fork of
> FFmpeg that branched off early this year. I put together a quick
> initial formula, but I've run into a problem I don't remember seeing
> anywhere so far - both packages conflict with each other. Both of them
> currently use the `ffmpeg` name for their bins (LibAV is transitioning
> towards an `avconv` executable, but `ffmpeg` is still in use for the
> time being), and both of them use the same names for their standard
> libraries (such as `libavcodec`) despite diverging APIs.
>
> Unfortunately this isn't a cut-and-dry fork like Xfree86 vs X.org,
> since both projects are still under very active development now. Any
> thoughts on how we want to handle this? I can see a few possible
> options:
>
> - Add LibAV as a keg-only formula, let users manage their own symlinks
> - Make one or both formulae install their libs to libexec, rename bins
> to avoid conflicts, and modify formulae that depend on them to handle
> linking
> - Add a `conflicts` field to the DSL, and track this in metadata when
> metadata support is added; add conflict detection to `brew install`
> - Don't add LibAV (or other incompatible forks), stick with one project only
>
> Misty
Re: [homebrew] LibAV conflicts with FFmpeg - thoughts?
- From:
- Mike McQuaid
- Date:
- 2011-10-25 @ 08:42
On 24 Oct 2011, at 16:22, Misty De Meo wrote:
> - Add LibAV as a keg-only formula, let users manage their own symlinks
This option works while it's not used as much as ffmpeg.
> - Make one or both formulae install their libs to libexec, rename bins
> to avoid conflicts, and modify formulae that depend on them to handle
> linking
I really don't like this.
> - Add a `conflicts` field to the DSL, and track this in metadata when
> metadata support is added; add conflict detection to `brew install`
I don't think this is necessary unless we have a lot more formulae that
require it. Even then, you could just run a command that checks for ffmpeg
and causes the installation to fail if it's installed instead.
> - Don't add LibAV (or other incompatible forks), stick with one project only
I'm in favour if this now unless people are clamouring for it.
--
Mike McQuaid
http://mikemcquaid.com
Re: [homebrew] LibAV conflicts with FFmpeg - thoughts?
- From:
- Max Howell
- Date:
- 2011-10-25 @ 09:07
>> - Add a `conflicts` field to the DSL, and track this in metadata when
>> metadata support is added; add conflict detection to `brew install`
>
> I don't think this is necessary unless we have a lot more formulae that
require it. Even then, you could just run a command that checks for ffmpeg
and causes the installation to fail if it's installed instead.
This is probably the easiest move for now.
Though we do have other formula that conflict, and we don't simply
design for us, we design for utility so forks can do what they want.