nixpkgs/pkgs/tools/misc/mmctl/default.nix

{ mattermost
}:

mattermost.overrideAttrs (o: {
  pname = "mmctl";
  subPackages = [ "cmd/mmctl" ];

  meta = o.meta // {
    description = "A remote CLI tool for Mattermost";
    mainProgram = "mmctl";
  };
})
mmctl: 9.2.2 → 9.5.1, use override on mattermost This makes the mmctl package be an override on the mattermost package, as these were both moved by upstream into the same monorepo and use the same build system. Nevertheless, it makes sense to keep them in separate packages, as the mmctl utility is usually used on a different machine than the mattermost server. The meta information is retained as it was before (via an override). 2024-02-27 19:38:04 +01:00			`{ mattermost`
mmctl: 6.4.2 -> 7.0.0 2022-06-21 02:10:26 +02:00			`}:`

mmctl: 9.2.2 → 9.5.1, use override on mattermost This makes the mmctl package be an override on the mattermost package, as these were both moved by upstream into the same monorepo and use the same build system. Nevertheless, it makes sense to keep them in separate packages, as the mmctl utility is usually used on a different machine than the mattermost server. The meta information is retained as it was before (via an override). 2024-02-27 19:38:04 +01:00			`mattermost.overrideAttrs (o: {`
mmctl: init at 6.2.1 2021-12-22 12:12:27 +01:00			`pname = "mmctl";`
mmctl: 7.10.5 -> 9.2.2 (#269709) 2023-11-30 04:30:28 +01:00			`subPackages = [ "cmd/mmctl" ];`
mmctl: init at 6.2.1 2021-12-22 12:12:27 +01:00
mmctl: 9.2.2 → 9.5.1, use override on mattermost This makes the mmctl package be an override on the mattermost package, as these were both moved by upstream into the same monorepo and use the same build system. Nevertheless, it makes sense to keep them in separate packages, as the mmctl utility is usually used on a different machine than the mattermost server. The meta information is retained as it was before (via an override). 2024-02-27 19:38:04 +01:00			`meta = o.meta // {`
mmctl: init at 6.2.1 2021-12-22 12:12:27 +01:00			`description = "A remote CLI tool for Mattermost";`
treewide: add mainProgram 2023-11-27 02:17:53 +01:00			`mainProgram = "mmctl";`
mmctl: init at 6.2.1 2021-12-22 12:12:27 +01:00			`};`
mmctl: 9.2.2 → 9.5.1, use override on mattermost This makes the mmctl package be an override on the mattermost package, as these were both moved by upstream into the same monorepo and use the same build system. Nevertheless, it makes sense to keep them in separate packages, as the mmctl utility is usually used on a different machine than the mattermost server. The meta information is retained as it was before (via an override). 2024-02-27 19:38:04 +01:00			`})`