4 commits

Author	SHA1	Message	Date
Profpatsch	4a7f99d55d	treewide: with stdenv.lib; in meta -> with lib; ... Part of: https://github.com/NixOS/nixpkgs/issues/108938 meta = with stdenv.lib; is a widely used pattern. We want to slowly remove the `stdenv.lib` indirection and encourage people to use `lib` directly. Thus let’s start with the meta field. This used a rewriting script to mostly automatically replace all occurances of this pattern, and add the `lib` argument to the package header if it doesn’t exist yet. The script in its current form is available at https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix	2021-01-11 10:38:22 +01:00
rnhmjoj	6545e5a506	pkgs/data/fonts: merge back the split otb output ... Since the Pango issue 457[1] has been fixed and Nixpkgs patched, it's no longer necessary to keep X11 and .otb fonts in separate outputs (previously they would cause application to display broken fonts). [1]: https://gitlab.gnome.org/GNOME/pango/-/issues/457	2020-08-22 09:45:05 +02:00
wishfort36	1975e4b2ec	tamzen: 1.11.4 -> 1.11.5 ... Pango doesn't support PCF and BDF fonts since v1.44 [1], but still supports OTB fonts. As such, we've had to generate OTB fonts for fonts that don't supply them [2], including tamzen. As of v1.11.5, tamzen supplies its own OTB fonts [3], so we don't need to make them ourselves. [1]: https://gitlab.gnome.org/GNOME/pango/-/issues/386 [2]: https://github.com/NixOS/nixpkgs/issues/75160 [3]: https://github.com/sunaku/tamzen-font/issues/25	2020-05-27 09:01:22 -07:00
wishfort36	c7551f47c2	tamzen: init at 1.11.4	2020-05-18 21:01:48 +02:00