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

boost-build: update to version 2016.03 #26903

Merged
merged 2 commits into from Jun 28, 2017
Merged

Conversation

ivan-tkatchev
Copy link
Contributor

Motivation for this change

Boost-build as currently in nixpkgs is severely out of date. (Missing support for clang, for example.)

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
    • Linux
  • 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.

src = fetchurl {
url = "mirror://sourceforge/boost/${name}.tar.bz2";
sha256 = "10sbbkx2752r4i1yshyp47nw29lyi1p34sy6hj7ivvnddiliayca";
name = "boost-build-2.0-${version}";
Copy link
Member

Choose a reason for hiding this comment

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

I think 2.0 can be dropped here, no?

Copy link
Member

@Mic92 Mic92 Jun 27, 2017

Choose a reason for hiding this comment

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

I am a little bit confused about the version schema. This tags seems newer: https://github.com/boostorg/build/releases/tag/boost-1.64.0
Which version is preferred?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, the "2.0" can be probably dropped, even though it's not really a version number, it's the name of the project after a refactoring effort.

Boost Build releases are not tied to Boost releases, I'm not sure why they have Boost version tags in the repo, but it's probably not a good idea to use them when Boost Build isn't being bundled with Boost itself.

@Mic92
Copy link
Member

Mic92 commented Jun 28, 2017

Thanks!

@Mic92 Mic92 merged commit 5e044b9 into NixOS:master Jun 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants