about summary refs log tree commit diff
path: root/pkgs/applications/networking/cluster/habitat
AgeCommit message (Collapse)AuthorFilesLines
2023-08-23habitat: add qjoly as maintainerQJoly1-1/+1
2023-08-23habitat: 1.6.652 -> 1.6.848QJoly2-575/+967
2023-05-12habitat: 0.90.6 -> 1.1.652, fix build, unpin opensslfigsoda2-2559/+2489
Diff: https://github.com/habitat-sh/habitat/compare/0.90.6...1.6.652 Changelog: https://github.com/habitat-sh/habitat/blob/1.6.652/CHANGELOG.md
2023-03-26tree-wide: convert rust with git deps to importCargoLockYureka2-1/+4382
2021-05-08treewide: fix cargoSha256/cargoHashDaniël de Kok1-1/+1
Rust 1.50.0 incorporated a Cargo change (rust-lang/cargo#8937) in which cargo vendor erroneously changed permissions of vendored crates. This was fixed in Rust 1.51.0 (rust-lang/cargo#9131). Unfortunately, this means that all cargoSha256/cargoHashes produced during the Rust 1.50.0 cycle are potentially broken. This change updates cargoSha256/cargoHash tree-wide. Fixes #121994.
2021-01-25treewide: remove stdenv where not neededPavol Rusnak1-1/+1
2021-01-16pkgs/applications: pkgconfig -> pkg-configBen Siraphob1-2/+2
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-03-16habitat: 0.30.2 -> 0.90.6Benjamin Hipple1-18/+13
The build has been broken on master for a very long time, for want of an upgrade. This continues the effort put forth here: https://github.com/NixOS/nixpkgs/pull/63105 Note that while there are newer versions than this, upgrading to those requires getting some Cargo protobuf dependencies to compile. Since this fixes the failing build, it seems like a good start. Upstream does not appear to have any Darin builds in their CI, and we do not have a Darwin maintainer available, so this disables it as well.
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-08-31treewide: name -> pname (#67513)volth1-1/+1
2018-07-21pkgs/*: remove unreferenced function argumentsvolth1-1/+1
2017-10-23rust: update cargo builder to fetch registry dynamicallyKevin Cox1-1/+2
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-08-29habitat: 0.8.0 -> 0.30.2rushmorem2-14/+12
2016-07-14habitat: fix naming collisionrushmorem1-1/+1
2016-07-14habitat: add an option to run in an FHS chrootrushmorem2-3/+12
`hab studio enter` as well as other `hab` commands that make use of the studio assume an FHS system when creating a chroot. See https://github.com/habitat-sh/habitat/issues/994
2016-06-27habitat: build from sourcerushmorem1-25/+14
2016-06-25habitat: init at 0.7.0rushmorem1-0/+43