nixpkgs-suyu/pkgs/tools/filesystems/file-rename/default.nix

{ lib, stdenv, fetchurl, perl, perlPackages }:

perlPackages.buildPerlPackage {
  pname = "File-Rename";
  version = "0.20";

  src = fetchurl {
    url = "mirror://cpan/authors/id/R/RM/RMBARKER/File-Rename-0.20.tar.gz";
    sha256 = "1cf6xx2hiy1xalp35fh8g73j67r0w0g66jpcbc6971x9jbm7bvjy";
  };

  # Fix an incorrect platform test that misidentifies Darwin as Windows
  postPatch = ''
    substituteInPlace Makefile.PL \
      --replace '/win/i' '/MSWin32/'
  '';

  postFixup = ''
    substituteInPlace $out/bin/rename \
      --replace "#!${perl}/bin/perl" "#!${perl}/bin/perl -I $out/${perl.libPrefix}"
  '';

  doCheck = !stdenv.isDarwin;

  meta = with lib; {
    description = "Perl extension for renaming multiple files";
    license = licenses.artistic1;
    maintainers = with maintainers; [ peterhoeg ];
  };
}
treewide: use perl.withPackages when possible Since 03eaa48 added perl.withPackages, there is a canonical way to create a perl interpreter from a list of libraries, for use in script shebangs or generic build inputs. This method is declarative (what we are doing is clear), produces short shebangs[1] and needs not to wrap existing scripts. Unfortunately there are a few exceptions that I've found: 1. Scripts that are calling perl with the -T switch. This makes perl ignore PERL5LIB, which is what perl.withPackages is using to inform the interpreter of the library paths. 2. Perl packages that depends on libraries in their own path. This is not possible because perl.withPackages works at build time. The workaround is to add `-I $out/${perl.libPrefix}` to the shebang. In all other cases I propose to switch to perl.withPackages. [1]: https://lwn.net/Articles/779997/ 2021-02-24 20:53:45 +01:00			`{ lib, stdenv, fetchurl, perl, perlPackages }:`
perl.FileRename: init at 0.20 2018-02-04 14:32:09 +01:00
buildPerlPackage: name -> (pname, version) 2019-06-20 15:07:56 +02:00			`perlPackages.buildPerlPackage {`
			`pname = "File-Rename";`
			`version = "0.20";`
perl.FileRename: init at 0.20 2018-02-04 14:32:09 +01:00
			`src = fetchurl {`
treewide: Per RFC45, remove all unquoted URLs 2020-04-01 03:11:51 +02:00			`url = "mirror://cpan/authors/id/R/RM/RMBARKER/File-Rename-0.20.tar.gz";`
perl.FileRename: init at 0.20 2018-02-04 14:32:09 +01:00			`sha256 = "1cf6xx2hiy1xalp35fh8g73j67r0w0g66jpcbc6971x9jbm7bvjy";`
			`};`

file-rename: Fix an incorrect platform test that misidentifies Darwin as Windows This causes the script to be installed as `file-rename` instead of `rename` like it is on other Unix systems. This in turn causes `wrapProgram` to fail when building because it expects the wrapped program to be called `rename`. 2020-06-28 01:45:28 +02:00			`# Fix an incorrect platform test that misidentifies Darwin as Windows`
			`postPatch = ''`
			`substituteInPlace Makefile.PL \`
			`--replace '/win/i' '/MSWin32/'`
			`'';`

treewide: use perl.withPackages when possible Since 03eaa48 added perl.withPackages, there is a canonical way to create a perl interpreter from a list of libraries, for use in script shebangs or generic build inputs. This method is declarative (what we are doing is clear), produces short shebangs[1] and needs not to wrap existing scripts. Unfortunately there are a few exceptions that I've found: 1. Scripts that are calling perl with the -T switch. This makes perl ignore PERL5LIB, which is what perl.withPackages is using to inform the interpreter of the library paths. 2. Perl packages that depends on libraries in their own path. This is not possible because perl.withPackages works at build time. The workaround is to add `-I $out/${perl.libPrefix}` to the shebang. In all other cases I propose to switch to perl.withPackages. [1]: https://lwn.net/Articles/779997/ 2021-02-24 20:53:45 +01:00			`postFixup = ''`
			`substituteInPlace $out/bin/rename \`
			`--replace "#!${perl}/bin/perl" "#!${perl}/bin/perl -I $out/${perl.libPrefix}"`
perl.FileRename: init at 0.20 2018-02-04 14:32:09 +01:00			`'';`

file-rename: don’t run tests on darwin https://hydra.nixos.org/build/92527786 2019-04-24 04:38:29 +02:00			`doCheck = !stdenv.isDarwin;`

treewide: with stdenv.lib; in meta -> with lib; 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 2021-01-11 08:54:33 +01:00			`meta = with lib; {`
perl.FileRename: init at 0.20 2018-02-04 14:32:09 +01:00			`description = "Perl extension for renaming multiple files";`
			`license = licenses.artistic1;`
perl.FileRename: fixup meta 2018-02-12 16:30:27 +01:00			`maintainers = with maintainers; [ peterhoeg ];`
perl.FileRename: init at 0.20 2018-02-04 14:32:09 +01:00			`};`
			`}`