Opened 13 years ago
Closed 13 years ago
#32594 closed update (wontfix)
ffmpeg: update to 0.9
| Reported by: | ranauei@… | Owned by: | dbevans (David B. Evans) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.3 |
| Keywords: | haspatch | Cc: | markus.doits@…, ranauei@… |
| Port: | ffmpeg |
Description
I updated this port to latest release and also I eliminated some useless dependencies like gmake and the necessity to select another compiler. I testet on my machine (MacBook Pro w/ 10.7.2 and Xcode 4.2.1 w/ Apple clang version 3.0 (tags/Apple/clang-211.12) (based on LLVM 3.0svn)) and it compiled fine. Also I moved the doc in a variant to further reduce the basic dependencies.
Attachments (2)
Change History (8)
comment:1 follow-up: 2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | changed from macports-tickets@… to devans@… |
|---|---|
| Summary: | Update ffmpeg from 0.7.8 to 0.9 → ffmpeg: update to 0.9 |
comment:2 Changed 13 years ago by ranauei@…
Replying to ryandesign@…:
Thank you but please attach a new patch that makes the minimum changes necessary -- in particular, don't change the whitespace of the Portfile because it makes it very difficult to review your patch.
Sorry once I noticed the use of spaces instead of tabs and other style flaws I got a bit carried away :P
As I recall, the problem with updating ffmpeg past 0.7.x is that the API changes; we would need to also verify that every port that uses ffmpeg still works with the new API, and increase the revision of each such port to force it to rebuild.
I don't know about this. I was creating a port for miniDLNA* and I noticed that ffmpeg wasn't up to date, so I modified the portfile to fix that.
*For now my port for miniDLNA uses cvs because latest stable doesn't compile easily on mac, I can add that port anyway. I think the only minor adjustement it needs is to add a fixed date to fetch the cvs from.
Changed 13 years ago by ranauei@…
| Attachment: | Portfile2.diff added |
|---|
New w/ minimum changes and sha256 hash
comment:6 Changed 13 years ago by raimue (Rainer Müller)
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Superseded by #33048.
Thank you but please attach a new patch that makes the minimum changes necessary -- in particular, don't change the whitespace of the Portfile because it makes it very difficult to review your patch.
As I recall, the problem with updating ffmpeg past 0.7.x is that the API changes; we would need to also verify that every port that uses ffmpeg still works with the new API, and increase the revision of each such port to force it to rebuild.