221d194cb7
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).
12 lines
211 B
Nix
12 lines
211 B
Nix
{ mattermost
|
|
}:
|
|
|
|
mattermost.overrideAttrs (o: {
|
|
pname = "mmctl";
|
|
subPackages = [ "cmd/mmctl" ];
|
|
|
|
meta = o.meta // {
|
|
description = "A remote CLI tool for Mattermost";
|
|
mainProgram = "mmctl";
|
|
};
|
|
})
|