-
-
Notifications
You must be signed in to change notification settings - Fork 13.4k
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
git: 2.10.0 -> 2.10.1 #19248
git: 2.10.0 -> 2.10.1 #19248
Conversation
@FRidh, thanks for your PR! By analyzing the history of the files in this pull request, we identified @phanimahesh, @peti and @edolstra to be potential reviewers. |
Why would updating git be a mass rebuild (it doesn't affect fetchgit output hashes)? |
Judging from the nox-review output there's still a great deal of packages affected by it. |
Yes, I was worried about that in my previous update to git, too. git depends on many things, (svn and tcl are among the not very obvious ones if i remember correctly), and somehow way too many things depend on git. |
How about this one, @vcunat re staging? |
The mass-rebuild label is intended for |
Perhaps not disagrees, but based on what he was saying it sounded like updates that trigger many rebuilds are candidates for staging to reduce friction for other contributions. Since this one did exactly that, I wanted his feedback. Edited to say: my understanding was the same, that staging was just for stdenv changes, and now I'm trying to suss out the finer points. |
It is a mass rebuild, unfortunately. The dependency chain starts like this: git -> fontforge -> dejavu_fonts -> fontconfig. (The last step here was introduced by me, relatively recently 4f73633.) |
fontconfig needs git to create a new mac os x release bundle. diff --git a/pkgs/tools/misc/fontforge/default.nix b/pkgs/tools/misc/fontforge/default.nix
index ba1154a..7517dc2 100644
--- a/pkgs/tools/misc/fontforge/default.nix
+++ b/pkgs/tools/misc/fontforge/default.nix
@@ -1,5 +1,5 @@
{ stdenv, fetchFromGitHub, fetchpatch, lib
-, autoconf, automake, gnum4, libtool, git, perl, gnulib, uthash, pkgconfig, gettext
+, autoconf, automake, gnum4, libtool, perl, gnulib, uthash, pkgconfig, gettext
, python, freetype, zlib, glib, libungif, libpng, libjpeg, libtiff, libxml2, pango
, withGTK ? false, gtk2
, withPython ? true
@@ -17,6 +17,9 @@ stdenv.mkDerivation rec {
sha256 = "15nacq84n9gvlzp3slpmfrrbh57kfb6lbdlc46i7aqgci4qv6fg0";
};
+ # git isn't really used, but configuration fails without it
+ GIT=/usr/bin/env;
+
patches = [(fetchpatch {
name = "use-system-uthash.patch";
url = "http://pkgs.fedoraproject.org/cgit/fontforge.git/plain/"
@@ -27,7 +30,7 @@ stdenv.mkDerivation rec {
# FIXME: git isn't really used, but configuration fails without it
buildInputs = [
- git autoconf automake gnum4 libtool perl pkgconfig gettext uthash
+ autoconf automake gnum4 libtool perl pkgconfig gettext uthash
python freetype zlib glib libungif libpng libjpeg libtiff libxml2
]
++ lib.optionals withGTK [ gtk2 pango ] |
That doesn't build for me. |
... but that's just due to sandboxing; the approach works in principle and I think we should take it. |
... to avoid git changes being mass rebuilds. Thanks to Mic92 for the solution idea. See discussion under: #19248
strange, I thought I have also sandbox enabled: # /etc/nixos/configuration.nix
nix = {
extraOptions = ''
build-use-sandbox = true
''
} |
Motivation for this change
Things done
(nix.useSandbox on NixOS,
or option
build-use-sandbox
innix.conf
on non-NixOS)
nix-shell -p nox --run "nox-review wip"
./result/bin/
)Not yet tested!