about summary refs log tree commit diff
path: root/pkgs/shells/ion
AgeCommit message (Collapse)AuthorFilesLines
2021-05-21ion: unstable-2020-03-22 -> unstable-2020-05-10happysalada1-5/+8
fix darwin build
2021-01-15pkgs/shells: stdenv.lib -> libBen Siraphob1-1/+1
2021-01-11treewide: with stdenv.lib; in meta -> with lib;Profpatsch1-2/+2
Part of: https://github.com/NixOS/nixpkgs/issues/108938 meta = with stdenv.lib; is a widely used pattern. We want to slowly remove the `stdenv.lib` indirection and encourage people to use `lib` directly. Thus let’s start with the meta field. This used a rewriting script to mostly automatically replace all occurances of this pattern, and add the `lib` argument to the package header if it doesn’t exist yet. The script in its current form is available at https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
2020-11-29ion: fix build on darwinRyan Burns1-1/+5
2020-08-16buildRustPackage: remove platform.all from packageszowoq1-1/+0
2020-03-27ion: 1.0.5 -> unstable-2020-03-22Benjamin Hipple1-11/+6
The app is still maintained upstream, but they aren't cutting releases on crates.io anymore: https://crates.io/crates/ion-shell This fixes the build with the latest Rust toolchain by upgrading to the current commit off the project's `master`. ZHF: #80379
2020-03-07ion: mark as brokenBenjamin Hipple1-6/+5
As noted in the comment, its Rust vendor directory no longer compiles. That said, we can still compute the new `cargoSha256`, and the package fails in precisely the same way.
2020-02-13treewide: change fetchCargoTarball default to opt-outBenjamin Hipple1-0/+3
Changes the default fetcher in the Rust Platform to be the newer `fetchCargoTarball`, and changes every application using the current default to instead opt out. This commit does not change any hashes or cause any rebuilds. Once integrated, we will start deleting the opt-outs and recomputing hashes. See #79975 for details.
2019-12-31Adding passthru to ion shell to allow using it as a login shell as advised ↵mox1-0/+4
for a similar case in https://github.com/NixOS/nixpkgs/issues/45830
2019-08-31treewide: name -> pname (#67513)volth1-1/+1
2019-06-01treewide: update cargoSha256 hashes for cargo-vendor upgradeAlyssa Ross1-1/+1
A recent upgrade of cargo-vendor changed its output slightly, which broke all cargoSha256 hashes in nixpkgs. See https://github.com/NixOS/nixpkgs/issues/60668 for more information. Since then, a few hashes have been fixed in master by hand, but there were a lot still to do, so I did all of the ones left over with some scripts I wrote. The one hash I wasn’t able to update was habitat's, because it’s currently broken and the build doesn’t get far enough to produce a hash anyway.
2018-09-03ion: broken on darwin (#46010)Vladyslav M1-0/+1
2017-10-23ion: 1.0.3 -> 1.0.5dywedir1-3/+3
2017-10-23rust: update cargo builder to fetch registry dynamicallyKevin Cox1-1/+1
The biggest benefit is that we no longer have to update the registry package. This means that just about any cargo package can be built by nix. No longer does `cargo update` need to be feared because it will update to packages newer then what is available in nixpkgs. Instead of fetching the cargo registry this bundles all the source code into a "vendor/" folder. This also uses the new --frozen and --locked flags which is nice. Currently cargo-vendor only provides binaries for Linux and macOS 64-bit. This can be solved by building it for the other architectures and uploading it somewhere (like the NixOS cache). This also has the downside that it requires a change to everyone's deps hash. And if the old one is used because it was cached it will fail to build as it will attempt to use the old version. For this reason the attribute has been renamed to `cargoSha256`. Authors: * Kevin Cox <kevincox@kevincox.ca> * Jörg Thalheim <Mic92@users.noreply.github.com> * zimbatm <zimbatm@zimbatm.com>
2017-07-09ion: init at 1.0.3dywedir1-0/+25