Commit Graph
37780 Commits
Author SHA1 Message Date
Dan Peebles 25e75cd580 kube-aws: 0.8.1 -> 0.9.4
Also, enable on Darwin
2017-03-13 22:20:52 -04:00
ndowens 706bd194c7 iso-codes: 3.56 -> 3.74 2017-03-13 20:29:03 -05:00
Tim Steinbach bb26805051 Merge pull request #23874 from NeQuissimus/kotlin_1_1
kotlin: 1.0.6 -> 1.1
2017-03-13 20:04:28 -04:00
Tim Steinbach 89c91c6e32 Merge pull request #23873 from NeQuissimus/gradle_3_4_1
gradle: 3.4.0 -> 3.4.1
2017-03-13 20:04:05 -04:00
Tim Steinbach dd015a829f kotlin: 1.0.6 -> 1.1 2017-03-13 20:03:39 -04:00
Tim Steinbach 56fea1a8c0 gradle: 3.4.0 -> 3.4.1 2017-03-13 20:00:58 -04:00
ndowens 64218d61fc hwloc: 1.11.2 -> 1.11.6 (#23870) 2017-03-14 00:44:28 +01:00
Vladimír Čunát bfed19cfaa Merge #23860: llvmPackages_4: rc4 -> release 2017-03-14 00:02:53 +01:00
Tuomas Tynkkynen aba0b45b86 Merge remote-tracking branch 'upstream/master' into staging
Conflicts:
      pkgs/development/libraries/qt-5/5.7/qtbase/default.nix
2017-03-14 00:49:22 +02:00
Lluís Batlle i Rossell 46c9eac980 guile: enable parallel building
civodul today on irc said that 2.0.13 likely has the parallel building
issue fixed (case equal-or-over 8 cores). Let's try.
2017-03-13 23:38:52 +01:00
Tim Steinbach 17978fe64c Merge pull request #23740 from ben-z/nodejs-7.7.2
nodejs: 7.7.1 -> 7.7.2
2017-03-13 18:14:32 -04:00
Tim Steinbach 2c1876ec6c Merge pull request #23844 from frontsideair/flow-41
flow: 0.39.0 -> 0.41.0
2017-03-13 18:12:16 -04:00
ndowens 4aee4cc8a5 htmlcxx: 0.85 -> 0.86 2017-03-13 17:11:03 -05:00
Tim Steinbach bc1f692e49 Merge pull request #23846 from mayflower/jenkins_2.49
jenkins: 2.44 -> 2.49
2017-03-13 18:09:19 -04:00
Tim Steinbach 6e0c3e1a6d Merge pull request #23862 from mimadrid/update/filezilla-3.25.0
filezilla: 3.24.0 -> 3.25.0
2017-03-13 17:58:34 -04:00
ndowens f3dab1a1e9 armadillo: 7.700.0 -> 7.800.0
armadillo: Added forgotton version update
2017-03-13 16:38:47 -05:00
Jörg Thalheim 065c05e849 Merge pull request #23801 from zimbatm/pip-tools
Pip tools
2017-03-13 22:32:07 +01:00
zimbatm a3c03eb11f pip-tools: init at 1.8.1rc3 2017-03-13 22:21:57 +01:00
mimadrid 7e9c815c23 libfilezilla: 0.9.0 -> 0.9.1 2017-03-13 22:17:08 +01:00
zimbatm 5e701625de pythonPackages.first: init at 2.0.1 2017-03-13 22:08:45 +01:00
Vincent Laporte 369230cc76 ocamlPackages.cpuid: init at 0.1.0
cpuid allows detection of CPU features from OCaml.

Homepage: https://github.com/pqwy/cpuid
2017-03-13 20:58:51 +00:00
Will Dietz f54813d767 llvm4: rc4 -> release! 2017-03-13 14:54:39 -05:00
Michael Raskin 90f2b24fd7 Merge pull request #23850 from makefu/update/radare2
radare2: 0.10.6 -> 1.3.0
2017-03-13 19:32:41 +01:00
Vincent Laporte b2b8a412fb ocaml-llvm: 3.7.1 -> 3.9.1 2017-03-13 19:14:11 +01:00
makefu bc1011b330 radare2: 0.10.6 -> 1.3.0 2017-03-13 17:53:12 +01:00
Frederik Rietdijk 57e768f58e hypothesis: 3.6.0 -> 3.6.1 2017-03-13 16:37:25 +01:00
Frederik Rietdijk 6f90badeac pythonPackages.hypothesis: fix for python 3.3 2017-03-13 16:37:24 +01:00
Tristan Helmich 4efed1d0d4 jenkins: 2.44 -> 2.49 2017-03-13 15:43:06 +01:00
Fatih Altinok d23effdedf flow: 0.39.0 -> 0.41.0 2017-03-13 17:04:36 +03:00
Domen Kožar 609f2fefce Merge pull request #23836 from expipiplus1/jailbreak-strict-io
Haskell Packages: jailbreak strict-io
2017-03-13 13:27:37 +01:00
Joe Hermaszewski 0867ac9963 Haskell Packages: jailbreak strict-io 2017-03-13 11:27:08 +00:00
Robin Gloster dbbdccdd65 ispc: fix build 2017-03-13 12:07:48 +01:00
Robin Gloster 80bd50a6e4 ponyc: 0.10.0 -> 0.11.0 2017-03-13 11:43:24 +01:00
Robin Gloster c836651084 purePackages.octave: 0.7 -> 0.9 2017-03-13 11:03:52 +01:00
Michael Raskin a77380b34c Merge pull request #23780 from asppsa/pure-0.66
pure: 0.64 -> 0.66
2017-03-13 10:56:08 +01:00
Vladimír Čunát b264486cf1 gnutls: bugfix+security 3.5.9 -> 3.5.10
http://gnutls.org/security.html#GNUTLS-SA-2017-3
2017-03-13 10:28:53 +01:00
Robin Gloster 89747d357b msilbc: fix build 2017-03-13 09:33:15 +01:00
Lancelot SIX 37794d7101 gdbm: 1.12 -> 1.13
See http://lists.gnu.org/archive/html/info-gnu/2017-03/msg00005.html
for release anouncement
2017-03-13 09:20:47 +01:00
Michael Raskin 7dc3edaa6a slimerjs: 0.10.2 -> 0.10.3 2017-03-13 08:23:52 +01:00
ndowens afeb989c5c gtkspell:3.0.8 -> 3.0.9 2017-03-12 20:38:46 -05:00
ndowens b64c6b46b1 gssdp: 0.14.11 -> 1.0.1 2017-03-12 19:41:00 -05:00
ndowens 86a23bcfff gmm: 4.3 -> 5.1
gmm: Remove whitespace
2017-03-12 18:51:15 -05:00
Michael Raskin 54b7c3b63f clisp-git: update to the upstream fix of 32-bit builds
The current exact tip fails to build on x86_64, there probably is a
fresher safe commit, but I haven't try bisecting.
2017-03-13 00:00:13 +01:00
ndowens a2d50e744a gloox: 1.0.14 -> 1.0.20 2017-03-12 17:56:33 -05:00
Thomas Tuegel 65592837b6 freetype: 2.6.5 -> 2.7.1
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
2017-03-12 17:31:33 -05:00
Jörg Thalheim ceeb0de60c Merge pull request #23773 from ndowens/cdk
cdk:5.0-20160131 -> 5.0-20161210
2017-03-12 23:16:19 +01:00
Vladimír Čunát 848423f223 clisp-tip: make the build more reliable
Hydra shows it sometimes fails without autoconf:
http://hydra.nixos.org/job/nixos/trunk-combined/nixpkgs.clisp-tip.x86_64-linux
I can't say I understand why this happened.
2017-03-12 23:07:55 +01:00
Benno Fünfstück 6c99f88eec fix typo in comment 2017-03-12 22:47:28 +01:00
Benno Fünfstück 039c6a6dfa haskell: comment about configuration-nix.nix's intersectAttrs 2017-03-12 22:45:19 +01:00
obadz 1dd16a9374 coreclr: mark broken 2017-03-12 21:32:27 +00:00