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

Update default attributes to latest version available #40015

Open
matthewbauer opened this issue May 5, 2018 · 7 comments

Comments

@matthewbauer
Copy link
Member

commented May 5, 2018

This is a tracking issue for old top-level attributes when the newest version is not being used. The usual policy is to make the generic attribute point to the latest version available & specify the older versions as arguments to callPackage where needed. There are legitimate exceptions but always good to try to get the latest software. Most of the exceptions have to do with `core' attributes like gcc or llvm where we need to be very careful when updating to avoid mass rebuilds & potential breakage.

  • ansible: 2.4 -> 2.5
  • antlr: 2.7.7 -> 4.7
  • buildkite-agent: 2 -> 3
  • libwnck: 2 → 3
  • python: 2 -> 3 (#18185)
  • premake: 4 -> 5
  • spidermonkey: 31 -> 52
  • zabbix: 1.8 -> 3.4
  • nodejs: 6.14.1 -> 9.11.1 (#40264)
  • mono: 4.4 -> 5.8
  • v8: 5.4.232 -> 6.2.414.27 (#60348)
  • libxmlxx: 2.40.1 -> 3.0.1
  • entropy
  • enchant: 1.6.1 -> 2.2.3 (#60348)
  • boost: 1.6.7 -> 1.7.0
  • wxGTK: 2.8 -> 3.1
  • llvm: 7 -> 8
  • gcc: 8 -> 9
  • postgres: 9.6 -> 11
  • ocaml: -> 4.07
  • openimageio: 1 → 2
  • icu: 59 -> 63 (64?)
  • opencv: 2.x -> 4.0.1

This is not a complete list. Additions are welcome!

I am looking into making a script to finding these using nix-env -qaP but it is still a work in progress. All of the above were generated manually.

@matthewbauer matthewbauer added this to To do in Picking up garbage via automation May 5, 2018

@FRidh

This comment has been minimized.

Copy link
Member

commented May 9, 2018

Mapping python to python3 was discussed in #18185 and on the mailing list. On the list there was a lot of opposition. But, at one point there was a working branch that did not break any builds and I was using that branch for some time.

@Mic92

This comment has been minimized.

Copy link
Contributor

commented May 10, 2018

ansible 2.4 is the latest release. 2.5 is currently under active development https://docs.ansible.com/ansible/2.4/release_and_maintenance.html#release-status

@rnhmjoj

This comment has been minimized.

Copy link
Contributor

commented May 12, 2018

If I understand correctly people are against it because PEP 394 recommends to symlink python to python2 with the rationale being to preserve compatibility with existing python2 script.
But don't we patch shebang to point to a very specific python interpreter already? Also this document is from 2011: python2 EOL now is only 1.5 years away. What do people expect it will happen after this date?

@FRidh

This comment has been minimized.

Copy link
Member

commented May 12, 2018

@rnhmjoj please discuss Python in #18185

@rnhmjoj

This comment has been minimized.

Copy link
Contributor

commented May 12, 2018

@FRidh Ah, sorry.

@matthewbauer matthewbauer added this to the 19.03 milestone Nov 5, 2018

@dtzWill

This comment has been minimized.

Copy link
Contributor

commented Jan 31, 2019

boost is another one for the list :).

@lilyball

This comment has been minimized.

Copy link
Member

commented May 15, 2019

OCaml should probably be on this list. nixpkgs.ocaml is 4.06, as is nixpkgs.ocamlPackages (which is really nixpkgs.ocaml-ng.ocamlPackages). Maybe there's a reason for holding it back, I don't know, I'm not an OCaml programmer, but the OCaml releases page doesn't indicate that 4.06 is any kind of LTS version, and the install page recommends 4.07.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
6 participants
You can’t perform that action at this time.