summary refs log tree commit diff
path: root/pkgs/development/libraries/cairo
Commit message (Collapse)AuthorAge
* cairo: enable GL support on 32-bit ARM and MIPSBen Wolsieffer2019-12-02
| | | | Mesa works fine on ARM now and this can result in obscure ARM specific bugs.
* treewide: Get rid of libGLU_combinedadisbladis2019-11-18
|
* treewide: name -> pnamevolth2019-08-17
|
* treewide: remove libGLSupported from pkgsMatthew Bauer2019-06-17
| | | | This isn’t a package, and we already have mesaPlatforms to handle this logic.
* cairo: make x11 optional, disabled on darwinJorge Acereda2019-04-18
|
* cairo: fix crossSymphorien Gibol2019-04-16
|
* cairo: use buildInputs for librariesMatthew Bauer2019-03-02
|
* Merge branch 'staging-next'Vladimír Čunát2019-02-20
|\ | | | | | | | | | | | | This round is without the systemd CVE, as we don't have binaries for that yet. BTW, I just ignore darwin binaries these days, as I'd have to wait for weeks for them.
| * Merge #55894: cairo: apply patch for CVE-2018-19876worldofpeace2019-02-17
| | | | | | | | | | | | (cherry picked from commit bad2db31b7b256e7b26f60e18dd2301cd277880c) Forward-picked from staging to staging-next; it's a trivial patch and we now rebuild anyway due to unzip.
* | cairo: move defaults to package fileJan Malakhovski2019-02-03
|/
* cairo: 1.15.14 -> 1.16.0Will Dietz2018-10-30
|
* cairo: 1.15.12 -> 1.15.14Will Dietz2018-09-25
|
* pkgs/*: remove unreferenced function argumentsvolth2018-07-21
|
* treewide: http -> https sources (#42676)Silvan Mosberger2018-06-28
| | | | | | | | | * treewide: http -> https sources This updates the source urls of all top-level packages from http to https where possible. * buildtorrent: fix url and tab -> spaces
* cairo: 1.15.10 -> 1.15.12Orivej Desh2018-05-30
| | | | | | The previous 1.15.10 (and the stable 1.14.12) have the bug https://bugs.freedesktop.org/show_bug.cgi?id=104325 which breaks perlPackages.Cairo and pythonPackages.cairocffi tests.
* tree-wide: disable `doCheck` and `doInstallCheck` where it fails (the ↵Jan Malakhovski2018-04-25
| | | | trivial part)
* cairo: 1.14.10 → 1.15.10Jan Tojnar2018-04-12
|
* treewide: remove libintl hacksMatthew Bauer2018-03-22
|
* treewide: transition mesa to libGLU_combinedAlexander V. Nikolaev2018-02-24
|
* treewide: transition from mesa_noglu to libGLAlexander V. Nikolaev2018-02-24
|
* cairo: bugfix 1.14.8 -> 1.14.10Vladimír Čunát2017-06-17
|
* Get rid of all `with { inherit... }` and just used `let inherit...`John Ericson2017-03-30
| | | | | | The old forms presumably predates, or were made in ignorance of, `let inherit`. This way is better style as the scoping as more lexical, something which Nix can (or might already!) take advantage of.
* freetype: 2.6.5 -> 2.7.1Thomas Tuegel2017-03-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The Infinality bytecode interpreter is removed in favor of the new v40 TrueType interpreter. In the past, the Infinality interpreter provided support for ClearType-style hinting instructions while the default interpreter (then v35) provided support only for original TrueType-style instructions. The v40 interpreter corrects this deficiency, so the Infinality interpreter is no longer necessary. To understand why the Infinality interpreter is no longer necessary, we should understand how ClearType differs from TrueType and how the v40 interpreter works. The following is a summary of information available on the FreeType website [1] mixed with my own editorializing. TrueType instructions use horizontal and vertical hints to improve glyph rendering. Before TrueType, fonts were only vertically hinted; horizontal hints improved rendering by snapping stems to pixel boundaries. Horizontal hinting is a risk because it can significantly distort glyph shapes and kerning. Extensive testing at different resolutions is needed to perfect the TrueType hints. Microsoft invested significant effort to do this with its "Core fonts for the Web" project, but few other typefaces have seen this level of attention. With the advent of subpixel rendering, the effective horizontal resolution of most displays increased significantly. ClearType eschews horizontal hinting in favor of horizontal supersampling. Most fonts are designed for the Microsoft bytecode interpreter, which implements a compatibility mode with TrueType-style (horizontal and vertical) instructions. However, applying the full horizontal hints to subpixel-rendered fonts leads to color fringes and inconsistent stem widths. The Infinality interpreter implements several techniques to mitigate these problems, going so far as to embed font- and glyph-specific hacks in the interpreter. On the other hand, the v40 interpreter ignores the horizontal hinting instructions so that glyphs render as they are intended to on the Microsoft interpreter. Without the horizontal hints, the problems of glyph and kerning distortion, color fringes, and inconsistent stem widths--the problems the Infinality interpreter was created to solve--simply don't occur in the first place. There are also security concerns which motivate removing the Infinality patches. Although there is an updated version of the Infinality interpreter for FreeType 2.7, the lack of a consistent upstream maintainer is a security concern. The interpreter is a Turing-complete virtual machine which has had security vulnerabilities in the past. While the default interpreter is used in billions of devices and is maintained by an active developer, the Infinality interpreter is neither scrutinized nor maintained. We will probably never know if there are defects in the Infinality interpreter, and if they were discovered they would likely never be fixed. I do not think that is an acceptable situtation for a core library like FreeType. Dropping the Infinality patches means that font rendering will be less customizable. I think this is an acceptable trade-off. The Infinality interpreter made many compromises to mitigate the problems with horizontal hinting; the main purpose of customization is to tailor these compromises to the user's preferences. The new interpreter does not have to make these compromises because it renders fonts as their designers intended, so this level of customization is not necessary. The Infinality-associated patches are also removed from cairo. These patches only set the default rendering options in case they aren't set though Fontconfig. On NixOS, the rendering options are always set in Fontconfig, so these patches never actually did anything for us! The Fontconfig test suite is patched to account for a quirk in the way PCF fonts are named. The fontconfig option `hintstyle` is no longer configurable in NixOS. This option selects the TrueType interpreter; the v40 interpreter is `hintslight` and the older v35 interpreter is `hintmedium` or `hintfull` (which have actually always been the same thing). The setting may still be changed through the `localConf` option or by creating a user Fontconfig file. Users with HiDPI displays should probably disable hinting and antialiasing: at best they have no visible effect. The fontconfig-ultimate settings are still available in NixOS, but they are no longer the default. They still work, but their main purpose is to set rendering quirks which are no longer necessary and may actually be detrimental (e.g. setting `hintfull` for some fonts). Also, the vast array of font substitutions provided is not an appropriate default; the default setting should be to give the user the font they asked for. [1]. https://www.freetype.org/freetype2/docs/subpixel-hinting.html
* Revert "cairo: Add ApplicationServices as propagatedBuildInput"Daiderd Jordan2017-01-09
| | | | This reverts commit 0f67005c4a2651ab0d9a48468a4873cff3551b8b.
* cairo: Add ApplicationServices as propagatedBuildInputJohannes Bornhold2017-01-07
| | | | Noticed that it caused depending packages to fail, like librsvg, imagemagiv, graphviz.
* cairo: Add CoreText for darwinJohannes Bornhold2017-01-07
| | | | | This helps so that fonts are properly rendered in gtk when used with the backend "quartz".
* cairo: maintenance 1.14.6 -> 1.14.8Vladimír Čunát2016-12-10
|
* cairo: add patch to fix CVE-2016-9082Franz Pletz2016-11-03
| | | | cc #20078
* docdev -> devdocEelco Dolstra2016-09-01
| | | | | It's "developer documentation", not "documentation developer" after all.
* treewide: Shuffle outputsTuomas Tynkkynen2016-08-29
| | | | Make either 'bin' or 'out' the first output.
* cairo: add infinality patchesNikolay Amiantov2016-08-20
|
* cairo: build cairo-xlib even on DarwinVincent Laporte2016-04-19
|
* Merge branch 'master' into closure-sizeVladimír Čunát2016-04-01
|\ | | | | | | | | Beware that stdenv doesn't build. It seems something more will be needed than just resolution of merge conflicts.
| * webkitgtk: add darwin supportRyan Trinkle2016-03-30
| |
* | Merge staging into closure-sizeVladimír Čunát2015-11-20
|\| | | | | | | | | | | The most complex problems were from dealing with switches reverted in the meantime (gcc5, gmp6, ncurses6). It's likely that darwin is (still) broken nontrivially.
| * cairo: maintenance update 1.14.2 -> 1.14.4 (close #10778)Stéphane Jourdois2015-11-04
| |
* | cairo: reduce bin output, and fixup a referenceVladimír Čunát2015-10-28
| |
* | cairo: get rid of xlibs-wrapperVladimír Čunát2015-10-13
| |
* | Merge commit staging+systemd into closure-sizeVladimír Čunát2015-10-03
|\| | | | | | | Many non-conflict problems weren't (fully) resolved in this commit yet.
| * xlibs.xlibs: removeVladimír Čunát2015-09-15
| | | | | | | | | | | | It was really ugly that `xlibs.xlibs` meant something else than `xlibs`, especially when using `with xlibs`, such as in wine. Also, now `xlibs` is the same as `xorg`.
| * Use common licence attributes from lib/licenses.nixTobias Geerinckx-Rice2015-05-27
| | | | | | | | | | | | | | | | | | | | Many (less easily automatically converted) old-style strings remain. Where there was any possible ambiguity about the exact version or variant intended, nothing was changed. IANAL, nor a search robot. Use `with stdenv.lib` wherever it makes sense.
* | Merge 'staging' into closure-sizeVladimír Čunát2015-04-18
|\| | | | | | | | | | | | | | | - there were many easy merge conflicts - cc-wrapper needed nontrivial changes Many other problems might've been created by interaction of the branches, but stdenv and a few other packages build fine now.
| * cairo: maintenance updateVladimír Čunát2015-04-18
| | | | | | | | The removed patch was included in the release.
| * kill libiconvOr*Eric Seidel2015-02-07
| | | | | | | | | | | | | | | | | | | | | | Conflicts: pkgs/applications/networking/mailreaders/sup/default.nix pkgs/development/compilers/ghc/7.8.3-binary.nix pkgs/development/interpreters/php/5.3.nix pkgs/development/interpreters/ruby/patches.nix pkgs/development/libraries/cairo/default.nix pkgs/development/libraries/poppler/default.nix pkgs/top-level/all-packages.nix
| * cairo: pull an upstream patch to fix racketVladimír Čunát2014-11-28
| | | | | | | | | | Close #5165, #5166. Also enableParallelBuilding in racket.
| * cairo: major update 1.12.* -> 1.14.0Vladimír Čunát2014-10-19
| | | | | | | | | | | | ABI diff only suggest that one enum value got updated, which should be fine for us. http://upstream-tracker.org/compat_reports/cairo/1.12.16_to_1.14.0/abi_compat_report.html#Low_Risk_Problems
* | Merge 'staging' into multiple-outputsVladimír Čunát2014-08-23
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: pkgs/applications/audio/flac/default.nix pkgs/build-support/gcc-wrapper/builder.sh pkgs/development/libraries/apr-util/default.nix pkgs/development/libraries/apr/default.nix pkgs/development/libraries/atk/default.nix pkgs/development/libraries/freetype/default.nix pkgs/development/libraries/gdk-pixbuf/default.nix pkgs/development/libraries/glib/default.nix pkgs/development/libraries/glibc/2.17/builder.sh pkgs/development/libraries/glibc/2.17/locales.nix pkgs/development/libraries/libjpeg/default.nix pkgs/development/libraries/libogg/default.nix pkgs/development/libraries/libsamplerate/default.nix pkgs/development/libraries/libtiff/default.nix pkgs/development/libraries/libvorbis/default.nix pkgs/development/libraries/mesa/default.nix pkgs/development/libraries/pango/default.nix pkgs/development/web/nodejs/default.nix pkgs/os-specific/linux/pam/default.nix pkgs/os-specific/linux/systemd/default.nix pkgs/stdenv/generic/setup.sh pkgs/stdenv/linux/default.nix pkgs/top-level/all-packages.nix pkgs/top-level/release-small.nix
| * Fix some "meta.licenses" attributesEelco Dolstra2014-01-25
| |
| * pangomm: update, so we can drop older cairoVladimír Čunát2013-12-10
| |
* | Merge remote-tracking branch 'official/master' into multiple-outputsMathijs Kwik2013-09-11
|\| | | | | | | | | | | | | | | | | | | | | Conflicts: pkgs/development/libraries/cairo/default.nix pkgs/development/libraries/freetype/default.nix pkgs/development/libraries/glib/default.nix pkgs/development/libraries/libpng/default.nix pkgs/development/libraries/pango/default.nix pkgs/tools/typesetting/tex/texlive/default.nix pkgs/top-level/all-packages.nix