[arch-general] Move from libjpeg-turbo to mozjpeg
Hi there, Mozilla have made a fork of the libjpeg-turbo package called mozjpeg, which features improved encoding: https://blog.mozilla.org/research/2014/03/05/introducing-the-mozjpeg-project... I'd like to propose making the switch. The "library configuration defaults are the same as for libjpeg-turbo, in order to make transitions as painless as possible". A PKGBUILD can be found on the AUR: https://aur.archlinux.org/packages/mozjpeg/ Thanks for your consideration, N30N.
[2014-03-08 04:32:28 +0100] N30N:
When you take the existing libjpeg-turbo PKGBUILD, change a few lines, and remove the Contributor/Maintainer tags altogether, you're not showing much respect for the community.
I'd like to propose making the switch.
I'll happily discuss with anyone who has concrete arguments to offer. -- Gaetan
When you take the existing libjpeg-turbo PKGBUILD, change a few lines, and remove the Contributor/Maintainer tags altogether, you're not showing much respect for the community.
Apologies, that was not my intentions (this has be corrected).
N30N wrote:
Hi there,
Mozilla have made a fork of the libjpeg-turbo package called mozjpeg, which features improved encoding: https://blog.mozilla.org/research/2014/03/05/introducing-the-mozjpeg-project...
I'd like to propose making the switch. The "library configuration defaults are the same as for libjpeg-turbo, in order to make transitions as painless as possible". A PKGBUILD can be found on the AUR: https://aur.archlinux.org/packages/mozjpeg/
Thanks for your consideration, N30N.
-1. mozjpeg offers slightly improved compression at the cost of up to x10 increase in compression time (*). It may be something to consider later if they manage to improve the speed although they expect that it will always remain slower than libjpeg-turbo. Jerome (*) https://github.com/mozilla/mozjpeg/issues/13 -- mailto:jeberger@free.fr http://jeberger.free.fr Jabber: jeberger@jabber.fr
-1.
mozjpeg offers slightly improved compression at the cost of up to x10 increase in compression time (*). It may be something to consider later if they manage to improve the speed although they expect that it will always remain slower than libjpeg-turbo.
As I quoted before the "defaults are the same as for libjpeg-turbo". The optimisations are enabled for cjpeg and jpegtran but there's a "-fastcrush" option to disable the progressive scan optimization.
Am 08.03.2014 04:32, schrieb N30N:
Hi there,
Mozilla have made a fork of the libjpeg-turbo package called mozjpeg, which features improved encoding: https://blog.mozilla.org/research/2014/03/05/introducing-the-mozjpeg-project...
I'd like to propose making the switch. The "library configuration defaults are the same as for libjpeg-turbo, in order to make transitions as painless as possible". A PKGBUILD can be found on the AUR: https://aur.archlinux.org/packages/mozjpeg/
Thanks for your consideration, N30N.
It'd be better if they'd push their changes upstream. I don't see any point in forking here. -- Pierre Schmitz, https://pierre-schmitz.com
I don't see any point in forking here.
It's not just a one off patch, they are planning additional features and improvements (some of which are listed on the issue tracker). Also being on github lowers the barrier for contributions. So I think forking is understandable.
participants (4)
-
"Jérôme M. Berger"
-
Gaetan Bisson
-
N30N
-
Pierre Schmitz