Package Base Details: dav1d-git

Git Clone URL: (read-only, click to copy)
Submitter: linkmauve
Maintainer: atticf
Last Packager: atticf
Votes: 5
Popularity: 0.000000
First Submitted: 2018-09-22 13:21 (UTC)
Last Updated: 2023-10-29 02:36 (UTC)

Latest Comments

1 2 Next › Last »

Matr1x-101 commented on 2023-10-11 17:00 (UTC)

Can someone unflag this? This is a dev package

linkmauve commented on 2021-08-15 18:59 (UTC)

Liquorice, this package builds dav1d-git 0.9.1.r37.g0141476-1 currently, which is the latest available commit. If you have kept an old version, you just have to rebuild the package, no need for any change in the PKGBUILD, makepkg will bump the version according to the commit it is building.

linkmauve commented on 2021-03-06 20:04 (UTC)

Actually no, libplacebo only provides the soname .104 (provided by the version in community) while dav1dplay currently requires .110.

<deleted-account> commented on 2021-03-06 19:57 (UTC)

@linkmauve you can already lower libplacebo from libplacebo-git to the ordinary one which is available in the community repository.

Quantum1248 commented on 2021-02-12 12:37 (UTC)

@linkmauve I can't compile with -flto enabled on manjaro. It worked fine last time I upgraded, 1-2 week ago.

190n commented on 2020-05-10 23:06 (UTC)

@linkmauve Could you add '' to the 'provides' line in the PKGBUILD? That will fix ffmpeg's dependency, as it depends on ''

dbermond commented on 2019-01-16 20:41 (UTC)

@linkmauve Upstream now provides tagged releases. The package should use it in pkgver: git describe --long --tags | sed 's/\([^-]*-g\)/r\1/;s/-/./g'

dbermond commented on 2018-11-28 12:27 (UTC)

@linkmauve This message appears only if you keep your old build tree. When building in a clean tree this message is not shown. Meson should be kept in build().

linkmauve commented on 2018-11-23 23:38 (UTC)

Hi, and thanks for your comment, I’ve applied all of your recommendations.

I do wonder about calling meson in build() though, since meson prints a message about the directory already being configured, and recommending to use ninja reconfigure instead; should I put back meson in prepare() and call ninja reconfigure all the time instead, in the case of an incompatible meson update for instance?

dbermond commented on 2018-11-23 11:07 (UTC)

@linkmauve You should not call meson in prepare(), but in build().

Also, you should use the arch-meson wrapper instead of calling meson directly. The wrapper automatically sets all the options that are used in Arch Linux, like the /usr prefix. You can take a look at packages that use it the official repositories, like libva and egl-wayland.

BSD is not a custom license, and should be referenced simply as 'BSD'.