Skip to content

boost: add version 1.76 #120132

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.

Sign up for GitHub

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

Closed
hjones2199 wants to merge 1 commit into from
Closed

boost: add version 1.76 #120132

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions pkgs/development/libraries/boost/1.76.nix
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
{ callPackage, fetchurl, fetchpatch, ... } @ args:

callPackage ./generic.nix (args // rec {
version = "1.76.0";

src = fetchurl {
urls = [
"mirror://sourceforge/boost/boost_1_76_0.tar.bz2"
"https://dl.bintray.com/boostorg/release/1.76.0/source/boost_1_76_0.tar.bz2"
];
# SHA256 from http://www.boost.org/users/history/version_1_76_0.html
Comment on lines +8 to +11
Copy link
Member

@SuperSandro2000 SuperSandro2000 Apr 22, 2021

Choose a reason for hiding this comment

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

Why are those version numbers not substituted?

Copy link
Member Author

@hjones2199 hjones2199 Apr 22, 2021 •
edited
Loading

Choose a reason for hiding this comment

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

I think because nixpkgs carries every version of boost starting with 1.55, the version-specific files aren't generalized since they are effectively "pinned" forever.

Copy link
Member Author

@hjones2199 hjones2199 Apr 22, 2021 •
edited
Loading

Choose a reason for hiding this comment

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

Perhaps it would be better to start fetching from https://github.com/boostorg/boost/releases instead of their sourceforge mirrors? Also i'm not sure why nixpkgs "default boost" is still 1.6. I can try to bump it, but this PR will need to go to staging or staging-next for that since it will be the mother of all mass rebuilds.

Copy link
Member

@SuperSandro2000 SuperSandro2000 Apr 24, 2021

Choose a reason for hiding this comment

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

Perhaps it would be better to start fetching from boostorg/boost/releases instead of their sourceforge mirrors?

I think that is a good idea for new releases. It also makes fetching patches easier.

Also i'm not sure why nixpkgs "default boost" is still 1.6.

Probably because many packages break if we change it.

this PR will need to go to staging

It will be staging and that is not a problem.

sha256 = "f0397ba6e982c4450f27bf32a2a83292aba035b827a5623a14636ea583318c41";
};
})
3 changes: 2 additions & 1 deletion pkgs/top-level/all-packages.nix
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13868,7 +13868,8 @@ in
boost173 = callPackage ../development/libraries/boost/1.73.nix { };
boost174 = callPackage ../development/libraries/boost/1.74.nix { };
boost175 = callPackage ../development/libraries/boost/1.75.nix { };
boost17x = boost175;
boost176 = callPackage ../development/libraries/boost/1.76.nix { };
boost17x = boost176;
boost = boost16x;

boost_process = callPackage ../development/libraries/boost-process { };
Expand Down