nixpkgs/pkgs/top-level/hare-third-party.nix

{ lib, newScope }:

lib.makeScope newScope (self:
let
  inherit (self) callPackage;
in
{
  hare-json = callPackage ../development/hare-packages/hare-json { };

  hare-compress = callPackage ../development/hare-third-party/hare-compress {};
})
hare: refactor `harePackages` into `hareThirdParty` The name `harePackages` may give thet impression that programs written in Hare should be added to its scope, which is not true: its purpose is to encapsulate Hare third party libraries. Thus, changing it to `hareThirdParty` makes it clear what its purpose is --- just like renaming `hare-packages.nix` to `hare-third-party.nix` on `pkgs/top-level`. Moreover, remove the `hare` and `harec` packages from the newly renamed `hareThirdParty` scope, since they are not Hare libraries. Finally, remove the inheritance of `harePackages.hare` on `himitsu` and `himitsu-firefox`, the two programs using `hare` on nixpkgs: both `hare` and `harec` are directly accessible since 12449072[1], when they were moved from `aliases.nix` to `all-packages.nix`, with the difference now that they do not belong anymore to `harePackages` --- now `hareThirdParty`. [1]: https://github.com/NixOS/nixpkgs/commit/1244907222bc7dc5cf4396544796afa6c14c2e52 2023-11-25 17:11:50 +01:00			`{ lib, newScope }:`

			`lib.makeScope newScope (self:`
			`let`
			`inherit (self) callPackage;`
			`in`
hareThirdParty.hare-json: init at unstable-2023-09-21 2023-12-03 17:14:38 +01:00			`{`
			`hare-json = callPackage ../development/hare-packages/hare-json { };`
hareThirdParty.hare-compress: init at unstable-2023-11-01 2023-12-13 12:20:19 +01:00
			`hare-compress = callPackage ../development/hare-third-party/hare-compress {};`
hareThirdParty.hare-json: init at unstable-2023-09-21 2023-12-03 17:14:38 +01:00			`})`