Leo Famulari <leo@famulari.name> writes:

> On Tue, Mar 05, 2019 at 03:12:07PM -0500, Leo Famulari wrote:
>> On Sat, Jan 19, 2019 at 12:13:49AM +0100, Arne Babenhauserheide wrote:
>> > +(define-public libaom
>> > +  (package
>> > +    (name "libaom")
>> > +    (version "22b150bf040608028a56d8bf39e72f771383d836") ;; master
>>
>> Typically we only package tagged releases. I think the latest libaom
>> release is 'v1.0.0-errata1'. Can we use that or did it not work for you?
>> If you didn't try it, I can do it here.
>
> To answer my own question, 1.0.0-errata1 installs a broken pkg-config
> .pc file [0].

Thank you for checking!
(I do not remember why I chose the commit instead of the tag)

> This is fixed in a later commit [1] ... we might as well use the commit
> you chose originally, which is later than the pkg-config fix commit.

Sounds good.

> This library's decoder is *very* expensive — it can't even decode
> 1280x720 in realtime on my Ivy Bridge i5-3230M. I'm sure it only gets
> faster as they keep working on it.

I take it that you did not test the encoder yet … it takes roughly an
hour per second :-)

But this is a reference for seeing the quality, not for fast de- and
encoding.

> I changed the libaom package to be more idiomatic about versioning from
> Git [2] and edited the synopsis and description, and pushed as
> 84eb265eb8076876d2b569bcdff1e44b44b4b295
>
> Thanks a lot!

Thank you for taking care of the patch!

Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken