Package Details: ffmpeg-libfdk_aac 1:4.1.3-1

Git Clone URL: https://aur.archlinux.org/ffmpeg-libfdk_aac.git (read-only)
Package Base: ffmpeg-libfdk_aac
Description: Complete solution to record, convert and stream audio and video (Same as official package except with libfdk-aac support)
Upstream URL: https://ffmpeg.org/
Licenses: GPL3, custom:libfdk-aac
Conflicts: ffmpeg
Provides: ffmpeg=4.1.3, libavcodec.so, libavdevice.so, libavfilter.so, libavformat.so, libavutil.so, libpostproc.so, libswresample.so, libswscale.so
Submitter: korrode
Maintainer: bwidawsk
Last Packager: bwidawsk
Votes: 45
Popularity: 0.428398
First Submitted: 2013-07-12 10:24
Last Updated: 2019-04-17 17:52

Dependencies (54)

Required by (867)

Sources (1)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Martchus commented on 2019-01-16 09:18

Upstream might use Git because it is only a big download for the first time. In any subsequent build you only have to fetch the diff (likely only a few KiB).

bwidawsk commented on 2019-01-16 04:39

By upstream, I mean the PKGBUILD

https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/ffmpeg

milaxnuts commented on 2019-01-13 19:01

I am trying to make the most minimal diff against upstream as possible. This does use release tags, not master

with "upstream" you mean http://ffmpeg.org/download.html#get-sources ?

there, the first link is /releases/ffmpeg-snapshot.tar.bz2
quote:

Development branch snapshots work really well 99% of the time so people are not afraid to use them.

quote from http://ffmpeg.org/download.html#releases

Users that wish to compile from source themselves are strongly encouraged to consider using the development branch [and not the stable release]

$ curl -sI <http://ffmpeg.org/releases/ffmpeg-snapshot.tar.bz2> \
| grep ^Content-Length | tr -d $'\r' | cut -d' ' -f2 | numfmt --to=si
11M

11 megabyte ... better than 130 MB, no?

this is ffmpeg-libfdk_aac, not ffmpeg-libfdk_aac-git.

to expand:
when i request ffmpeg-libfdk_aac, then i expect the latest stable release.
when i request ffmpeg-libfdk_aac-git, then i expect the 'bleeding edge' git version, compiled from a shallow clone, cos i only need 10% of the repo. since ffmpeg.org show no interest in fixing their git server, we could load the 'shallow clone' from microhub: https://github.com/FFmpeg/FFmpeg
when i request ffmpeg-libfdk_aac-snapshot, then i expect the 'latest snapshot' version.

bwidawsk commented on 2019-01-09 01:18

@milaxnuts: I completely agree with regard to shallow clone, but again I am trying to make the most minimal diff against upstream as possible. This does use release tags, not master, so I don't understand your first comment.

If you can get upstream to use a shallow clone when it works, I will gladly modify it here.

Thanks.

milaxnuts commented on 2019-01-06 22:57

easier to maintain the diff

please clarify

this is ffmpeg-libfdk_aac, not ffmpeg-libfdk_aac-git.
using the latest git version might break the build
so i would also prefer using the latest stable release.
im sure, new versions and checksums can be updated by bots

ffmpeg-full is also using the stable release
https://aur.archlinux.org/packages/ffmpeg-full/

also, doing a full clone of a 130 MB repo,
to only use 10 MB of code, is just wrong
so please just do a 'shallow clone' like

prepare() {
    # shallow clone. depth=1 might be too greedy
    # maybe add: --recurse-submodules --shallow-submodules
    git clone --mirror --depth=50 --branch v4.2 <https://host/path/name.git> name
}

currently, the git.ffmpeg.org server fails to serve a shallow clone
see https://trac.ffmpeg.org/ticket/7655

bwidawsk commented on 2018-10-10 18:02

@Niklas - this is mentioned in my commit. It was done to match the "upstream PKGBUILD" to make it easier to maintain the diff. I'm not sure why upstream did it as I agree with your preference for release tarballs.

commit 26942dcf6eb9

upgpkg: ffmpeg 1:4.0.2-1

Note that this follows the upstream package in switching to git for the source files (instead of tarball).

wookietreiber commented on 2018-10-10 16:09

+1 on high compatibility to upstream

bwidawsk commented on 2018-10-10 16:02

@Niklas - this is mentioned in my commit. It was done to match the "upstream PKGBUILD" to make it easier to maintain the diff. I'm not sure why upstream did it as I agree with your preference for release tarballs.

Niklas commented on 2018-10-10 15:55

Is there any specific reason for why this is using the git repository instead of a tarball? As far as I can tell, this package is only meant for stable versions, so I don't see any reason why using the git repo would be necessar (git takes more disk space and longer to download).

theYinYeti commented on 2018-08-19 10:10

Build failure:

ERROR: gnutls not found using pkg-config

If you think configure made a mistake, make sure you are using the latest
version from Git.  If the latest version fails, report the problem to the
ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
Include the log file "ffbuild/config.log" produced by configure as this will
help solve the problem.

bwidawsk commented on 2018-04-23 22:46

It was a mistake on my part that this got bumped before the official repo. I do not intend to do it again. I see no point in reverting now though.

Someone flagged this as out of date, and I didn't pay close enough attention when I pulled the official repo's sources.

For future reference, please do not flag this as out of date until the official repo is updated. Thanks.