nixpkgs/pkgs/by-name/wi/wiggle/package.nix
aleksana 571c71e6f7 treewide: migrate packages to pkgs/by-name, take 1
We are migrating packages that meet below requirements:

1. using `callPackage`
2. called path is a directory
3. overriding set is empty (`{ }`)
4. not containing path expressions other than relative path (to
makenixpkgs-vet happy)
5. not referenced by nix files outside of the directory, other
than`pkgs/top-level/all-packages.nix`
6. not referencing nix files outside of the directory
7. not referencing `default.nix` (since it's changed to `package.nix`)
8. `outPath` doesn't change after migration

The tool is here: https://github.com/Aleksanaa/by-name-migrate.
2024-11-09 20:04:51 +08:00

46 lines
1.5 KiB
Nix

{ lib, stdenv, fetchFromGitHub, ncurses, groff }:
stdenv.mkDerivation rec {
pname = "wiggle";
version = "1.3";
src = fetchFromGitHub {
owner = "neilbrown";
repo = "wiggle";
rev = "v${version}";
sha256 = "18ilzr9sbal1j8p1d94ilm1j5blac5cngvcvjpdmgmpw6diy2ldf";
};
buildInputs = [ ncurses groff ];
configurePhase = ''
makeFlagsArray=( CFLAGS="-I. -O3"
STRIP="-s"
INSTALL="install"
BINDIR="$out/bin"
MANDIR="$out/share/man"
)
patchShebangs .
'';
meta = with lib; {
homepage = "https://blog.neil.brown.name/category/wiggle/";
description = "Tool for applying patches with conflicts";
mainProgram = "wiggle";
longDescription = ''
Wiggle applies patches to a file in a similar manner to the patch(1)
program. The distinctive difference is, however, that wiggle will
attempt to apply a patch even if the "before" part of the patch doesn't
match the target file perfectly. This is achieved by breaking the file
and patch into words and finding the best alignment of words in the file
with words in the patch. Once this alignment has been found, any
differences (word-wise) in the patch are applied to the file as best as
possible. Also, wiggle will (in some cases) detect changes that have
already been applied, and will ignore them.
'';
license = licenses.gpl2Plus;
platforms = platforms.all;
maintainers = [ ];
};
}