Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

freetype: 2.9 -> 2.9.1 #52493

Closed
wants to merge 1 commit into from
Closed

Conversation

stephengroat
Copy link
Contributor

@stephengroat stephengroat commented Dec 18, 2018

freetype-config deprecated, manually enabled with new configureFlag

see http://lists.nongnu.org/archive/html/freetype-announce/2018-05/msg00000.html

Motivation for this change

closes #52415

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

freetype-config deprecated, manually enabled with new configureFlag

closes NixOS#52415
@@ -49,7 +49,7 @@ in stdenv.mkDerivation rec {

outputs = [ "out" "dev" ];

configureFlags = [ "--disable-static" "--bindir=$(dev)/bin" ];
configureFlags = [ "--disable-static" "--bindir=$(dev)/bin" "--enable-freetype-config" ];
Copy link
Contributor

@endgame endgame Dec 19, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like freetype's build system is also installing a pkg-config file, and I assume that if freetype-config is going away, downstream packages should be checking for freetype via pkg-config? How many packages in nixpkgs currently depend on freetype-config? Should there be issues created to track or fix those, or a comment here so we know when to remove this flag?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@endgame everything you said seems correct. i'm not sure now to track what packages currently use freetype-config other than testings all dependencies without including the binary and seeing what breaks

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe make a branch that's the version bump with no configure argument, and get someone to point hydra at it? I don't know who the correct person is, so I'm going to take a stab and ping @grahamc since ofborg has his name on things.

@grahamc hopefully you can add the right people and then unsub yourself. If my guess was wildly out-of-line, then I'm sorry.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hlandau
Copy link
Contributor

hlandau commented Jan 8, 2019

FYI, 2.9 is breaking PDF rendering (in e.g. mupdf-x11, Okular) for some PDFs, so this is kind of high-priority. 2.9.1 confirmed to fix.

Examples: https://i.imgur.com/PojSxTV.png
https://i.imgur.com/Ztj35oq.png

@stephengroat
Copy link
Contributor Author

closing since #52524 was merged

@stephengroat stephengroat deleted the patch-1 branch January 14, 2019 05:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

freetype: 2.9 -> 2.9.1
4 participants