Solved libx264 conflicts installs file in the same place

Hello,

For today's problem, we have:
Code:
pkg-static: libx264-0.142.2455 conflicts with x264-0.136.2358_4 (installs files into the same place).  Problematic file: /usr/local/include/x264.h

I get this when I try to upgrade multimedia/libx264. Anyone know how to fix it?
 
I saw that also. It looked like an earlier version of the same thing, so I just uninstalled the conflicting version and installed the new one. That's pretty haphazard, and I normally would not be quite that reckless, but there were other port issues that were more concerning.

The right way to do this is to enter a PR reporting the conflict. Either one port needs to be modified, or possibly an entry needs to be added to /usr/ports/UPDATING or /usr/ports/MOVED.
 
https://svnweb.freebsd.org/ports?view=revision&revision=373073

Code:
multimedia/x264: General overhaul

- Split x264 into two ports: the CLI application (x264), and the library
(libx264). This will allow x264 to use lavf and friends from ffmpeg for
decoding and demuxing while preventing a circular dependency between the
two: x264 can depend on ffmpeg, but ffmpeg will depend on libx264 rather
than x264.
- Add the LAVF option to the CLI port, making the dependency on ffmpeg
optional.
- Update to 0.142.2455.
- Amend fixes to local patches so that they can apply to the new upstream
files.
- Provide the git revision and other version information to the build
environment, allowing the CLI binary to display this information (like the
Windows builds).
- Remove unsupported build options (X11_OUTPUT).
- Ensure that the library and CLI ports each have the appropriate options.
- Add notes for future contributors who wish to update the ports.
- Bump PORTREVISION for all dependent ports.

PR: 187805
Differential Revision: https://reviews.freebsd.org/D1159
Submitted by: Andrew Berg <aberg010@my.hennepintech.edu>
Approved by: koobs (maintainer, mentor)
 
What do you mean by "Removing"? From /usr/ports? I try updating ffmpeg or libx264 and both complain about the same thing and renaming x264 didn't fix anything for me.

[ [port] tags require category/portname -- Mod ]
 
Back
Top