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

i2pd: 2.15.0 -> 2.17.0 #34063

Merged
merged 2 commits into from Jan 20, 2018
Merged

i2pd: 2.15.0 -> 2.17.0 #34063

merged 2 commits into from Jan 20, 2018

Conversation

corpix
Copy link
Contributor

@corpix corpix commented Jan 19, 2018

Motivation for this change

Updating to the last version of i2pd. Also this PR fixing the failing i2pd build(looks like boost version in nixpkgs is too fresh).

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-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/)
  • Fits CONTRIBUTING.md.

};

buildInputs = [ boost zlib openssl ];
buildInputs = [ boost165 zlib openssl ];
Copy link
Contributor

Choose a reason for hiding this comment

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

Thank you! Please override versions in all-packages.nix, like this:

blitz = callPackage ../development/libraries/blitz {
boost = boost160;
};

Copy link
Contributor Author

@corpix corpix Jan 19, 2018

Choose a reason for hiding this comment

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

Oops. Should I override derivations which have a version in the name like this(boost*, python*, python*Packages, ...) for every package I change? Is it a common approach? Asking because I have other PR where it is probably could be a good thing :)

Copy link
Contributor

Choose a reason for hiding this comment

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

This is mostly useful for tracking which derivations depend on older versions (that will be deleted in the future once no package depends on them) and trying to switch them to newer versions of their dependencies en masse. This does not quite apply to python (python3 can be seen as less an upgrade and more a different thing, like qt4 and qt5, gtk2 and gtk3, gnupg1 and gnupg, grub and grub2), so IMHO both approaches are fine, and AFAIK referring to python3 in Python 3 derivations is more prevalent.

@orivej orivej merged commit db56407 into NixOS:master Jan 20, 2018
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.

None yet

3 participants