Bug 234323 - multimedia/handbrake: update to 1.2.0
Summary: multimedia/handbrake: update to 1.2.0
Status: Closed DUPLICATE of bug 234322
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-12-24 04:50 UTC by Yuichiro NAITO
Modified: 2018-12-30 11:53 UTC (History)
0 users

See Also:

Attachments
handbrake-1.2.0.patch (12.97 KB, patch)
2018-12-24 04:50 UTC, Yuichiro NAITO 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yuichiro NAITO 2018-12-24 04:50:23 UTC 
Created attachment 200422 [details]
handbrake-1.2.0.patch

HandBrake 1.2.0 has been released.
This version includes following features and changes.

Runtime feature:
  - Backend library has been changed from libav to ffmpeg-4.1.
    Vulnerabilities of libav have been solved.
  - libx265 has been updated to 2.9.
  - Speex audio codec has been added for decode.

Buildtime change:
  - Assembler has been changed from yasm to nasm.
  - Clang compiler has been supported.
    USE_GCC is omitted.
    We no longer need libc++ link option.
  - BUILD_DEPENDS on binutils have been omitted.
    Our ld(1) has --exclude-libs option on all supported versions of FreeBSD.
  - Configure script respects $(CC) envrionment variable.
    We no longer need to patch config.py.
  - Configure script looks up python2 from $PATH.
    We no longer need to fix shebang.
  - Provides port specific patches by $(CP).
    To avoid patch of patches.

The attached `handbrake-1.2.0.patch` upgrades multimedia/handbrake port.
Please apply to Ports tree.
Thank you.
Comment 1 Yuichiro NAITO 2018-12-24 04:52:23 UTC 
I missed that I opened same bug report twice.
I'll close this.
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2018-12-30 11:53:51 UTC 
Correct resolution

*** This bug has been marked as a duplicate of bug 234322 ***