FS#42556 - [libx264] What criteria are you using to select a commit for release?
Attached to Project:
Arch Linux
Opened by John (graysky) - Saturday, 25 October 2014, 20:18 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 26 October 2014, 10:48 GMT
Opened by John (graysky) - Saturday, 25 October 2014, 20:18 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 26 October 2014, 10:48 GMT
|
Details
Just curious what criteria you are using to select a git
commit to use for the package. For example, if I look in the
upstream precompiled bins of the software[1], the latest
version they are offer is commit dd79a61e0e35 but our
package is an older commit (021c0dc6c95c). Thanks for any
insights.
1. http://download.videolan.org/pub/videolan/x264/binaries/linux-x86_64/ |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Sunday, 26 October 2014, 10:48 GMT
Reason for closing: Not a bug
Sunday, 26 October 2014, 10:48 GMT
Reason for closing: Not a bug
Comment by
Bartłomiej Piotrowski (Barthalion)
- Sunday, 26 October 2014, 10:45 GMT
It's obvious that it's newer, because it's built automatically. We
bump x264 only when new major ffmpeg release is out or new x264
commits don't break ABI.
Comment by
Bartłomiej Piotrowski (Barthalion)
- Sunday, 26 October 2014, 10:48 GMT
Also note that we use the stable branch, which points to commit
used in the package at the moment.