{ "content": [ { "type": "text", "text": "# File::Path (perldoc)\n\n## NAME\n\nFile::Path - Create or remove directory trees\n\n## SYNOPSIS\n\nuse File::Path qw(makepath removetree);\n@created = makepath('foo/bar/baz', '/zug/zwang');\n@created = makepath('foo/bar/baz', '/zug/zwang', {\nverbose => 1,\nmode => 0711,\n});\nmakepath('foo/bar/baz', '/zug/zwang', {\nchmod => 0777,\n});\n$removedcount = removetree('foo/bar/baz', '/zug/zwang', {\nverbose => 1,\nerror => \\my $errlist,\nsafe => 1,\n});\n# legacy (interface promoted before v2.00)\n@created = mkpath('/foo/bar/baz');\n@created = mkpath('/foo/bar/baz', 1, 0711);\n@created = mkpath(['/foo/bar/baz', 'blurfl/quux'], 1, 0711);\n$removedcount = rmtree('foo/bar/baz', 1, 1);\n$removedcount = rmtree(['foo/bar/baz', 'blurfl/quux'], 1, 1);\n# legacy (interface promoted before v2.06)\n@created = mkpath('foo/bar/baz', '/zug/zwang', { verbose => 1, mode => 0711 });\n$removedcount = rmtree('foo/bar/baz', '/zug/zwang', { verbose => 1, mode => 0711 });\n\n## DESCRIPTION\n\nThis module provides a convenient way to create directories of arbitrary depth and to delete an\nentire directory subtree from the filesystem.\n\n## Sections\n\n- **NAME**\n- **VERSION**\n- **SYNOPSIS**\n- **DESCRIPTION** (12 subsections)\n- **DIAGNOSTICS**\n- **SEE ALSO**\n- **BUGS AND LIMITATIONS**\n- **ACKNOWLEDGEMENTS**\n- **AUTHORS**\n- **CONTRIBUTORS**\n- **COPYRIGHT**\n- **LICENSE**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "File::Path", "section": "", "mode": "perldoc", "summary": "File::Path - Create or remove directory trees", "synopsis": "use File::Path qw(makepath removetree);\n@created = makepath('foo/bar/baz', '/zug/zwang');\n@created = makepath('foo/bar/baz', '/zug/zwang', {\nverbose => 1,\nmode => 0711,\n});\nmakepath('foo/bar/baz', '/zug/zwang', {\nchmod => 0777,\n});\n$removedcount = removetree('foo/bar/baz', '/zug/zwang', {\nverbose => 1,\nerror => \\my $errlist,\nsafe => 1,\n});\n# legacy (interface promoted before v2.00)\n@created = mkpath('/foo/bar/baz');\n@created = mkpath('/foo/bar/baz', 1, 0711);\n@created = mkpath(['/foo/bar/baz', 'blurfl/quux'], 1, 0711);\n$removedcount = rmtree('foo/bar/baz', 1, 1);\n$removedcount = rmtree(['foo/bar/baz', 'blurfl/quux'], 1, 1);\n# legacy (interface promoted before v2.06)\n@created = mkpath('foo/bar/baz', '/zug/zwang', { verbose => 1, mode => 0711 });\n$removedcount = rmtree('foo/bar/baz', '/zug/zwang', { verbose => 1, mode => 0711 });", "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [], "examples": [], "see_also": [], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "VERSION", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 28, "subsections": [] }, { "name": "DESCRIPTION", "lines": 5, "subsections": [ { "name": "make_path", "lines": 1 }, { "name": "make_path", "lines": 57 }, { "name": "mkpath", "lines": 1 }, { "name": "mkpath", "lines": 1 }, { "name": "mkpath", "lines": 1 }, { "name": "mkpath", "lines": 4 }, { "name": "remove_tree", "lines": 1 }, { "name": "remove_tree", "lines": 65 }, { "name": "rmtree", "lines": 1 }, { "name": "rmtree", "lines": 1 }, { "name": "rmtree", "lines": 1 }, { "name": "rmtree", "lines": 110 } ] }, { "name": "DIAGNOSTICS", "lines": 119, "subsections": [] }, { "name": "SEE ALSO", "lines": 12, "subsections": [] }, { "name": "BUGS AND LIMITATIONS", "lines": 32, "subsections": [] }, { "name": "ACKNOWLEDGEMENTS", "lines": 7, "subsections": [] }, { "name": "AUTHORS", "lines": 6, "subsections": [] }, { "name": "CONTRIBUTORS", "lines": 14, "subsections": [] }, { "name": "COPYRIGHT", "lines": 3, "subsections": [] }, { "name": "LICENSE", "lines": 3, "subsections": [] } ], "sections": { "NAME": { "content": "File::Path - Create or remove directory trees\n", "subsections": [] }, "VERSION": { "content": "2.18 - released November 4 2020.\n", "subsections": [] }, "SYNOPSIS": { "content": "use File::Path qw(makepath removetree);\n\n@created = makepath('foo/bar/baz', '/zug/zwang');\n@created = makepath('foo/bar/baz', '/zug/zwang', {\nverbose => 1,\nmode => 0711,\n});\nmakepath('foo/bar/baz', '/zug/zwang', {\nchmod => 0777,\n});\n\n$removedcount = removetree('foo/bar/baz', '/zug/zwang', {\nverbose => 1,\nerror => \\my $errlist,\nsafe => 1,\n});\n\n# legacy (interface promoted before v2.00)\n@created = mkpath('/foo/bar/baz');\n@created = mkpath('/foo/bar/baz', 1, 0711);\n@created = mkpath(['/foo/bar/baz', 'blurfl/quux'], 1, 0711);\n$removedcount = rmtree('foo/bar/baz', 1, 1);\n$removedcount = rmtree(['foo/bar/baz', 'blurfl/quux'], 1, 1);\n\n# legacy (interface promoted before v2.06)\n@created = mkpath('foo/bar/baz', '/zug/zwang', { verbose => 1, mode => 0711 });\n$removedcount = rmtree('foo/bar/baz', '/zug/zwang', { verbose => 1, mode => 0711 });\n", "subsections": [] }, "DESCRIPTION": { "content": "This module provides a convenient way to create directories of arbitrary depth and to delete an\nentire directory subtree from the filesystem.\n\nThe following functions are provided:\n", "subsections": [ { "name": "make_path", "content": "" }, { "name": "make_path", "content": "The \"makepath\" function creates the given directories if they don't exist before, much like\nthe Unix command \"mkdir -p\".\n\nThe function accepts a list of directories to be created. Its behaviour may be tuned by an\noptional hashref appearing as the last parameter on the call.\n\nThe function returns the list of directories actually created during the call; in scalar\ncontext the number of directories created.\n\nThe following keys are recognised in the option hash:\n\nmode => $num\nThe numeric permissions mode to apply to each created directory (defaults to 0777), to\nbe modified by the current \"umask\". If the directory already exists (and thus does not\nneed to be created), the permissions will not be modified.\n\n\"mask\" is recognised as an alias for this parameter.\n\nchmod => $num\nTakes a numeric mode to apply to each created directory (not modified by the current\n\"umask\"). If the directory already exists (and thus does not need to be created), the\npermissions will not be modified.\n\nverbose => $bool\nIf present, will cause \"makepath\" to print the name of each directory as it is created.\nBy default nothing is printed.\n\nerror => \\$err\nIf present, it should be a reference to a scalar. This scalar will be made to reference\nan array, which will be used to store any errors that are encountered. See the \"ERROR\nHANDLING\" section for more information.\n\nIf this parameter is not used, certain error conditions may raise a fatal error that\nwill cause the program to halt, unless trapped in an \"eval\" block.\n\nowner => $owner\nuser => $owner\nuid => $owner\nIf present, will cause any created directory to be owned by $owner. If the value is\nnumeric, it will be interpreted as a uid; otherwise a username is assumed. An error will\nbe issued if the username cannot be mapped to a uid, the uid does not exist or the\nprocess lacks the privileges to change ownership.\n\nOwnership of directories that already exist will not be changed.\n\n\"user\" and \"uid\" are aliases of \"owner\".\n\ngroup => $group\nIf present, will cause any created directory to be owned by the group $group. If the\nvalue is numeric, it will be interpreted as a gid; otherwise a group name is assumed. An\nerror will be issued if the group name cannot be mapped to a gid, the gid does not exist\nor the process lacks the privileges to change group ownership.\n\nGroup ownership of directories that already exist will not be changed.\n\nmakepath '/var/tmp/webcache', {owner=>'nobody', group=>'nogroup'};\n" }, { "name": "mkpath", "content": "" }, { "name": "mkpath", "content": "" }, { "name": "mkpath", "content": "" }, { "name": "mkpath", "content": "The \"mkpath()\" function provide the legacy interface of \"makepath()\" with a different\ninterpretation of the arguments passed. The behaviour and return value of the function is\notherwise identical to \"makepath()\".\n" }, { "name": "remove_tree", "content": "" }, { "name": "remove_tree", "content": "The \"removetree\" function deletes the given directories and any files and subdirectories\nthey might contain, much like the Unix command \"rm -rf\" or the Windows commands \"rmdir /s\"\nand \"rd /s\".\n\nThe function accepts a list of directories to be removed. (In point of fact, it will also\naccept filesystem entries which are not directories, such as regular files and symlinks.\nBut, as its name suggests, its intent is to remove trees rather than individual files.)\n\n\"removetree()\"'s behaviour may be tuned by an optional hashref appearing as the last\nparameter on the call. If an empty string is passed to \"removetree\", an error will occur.\n\nNOTE: For security reasons, we strongly advise use of the hashref-as-final-argument syntax\n-- specifically, with a setting of the \"safe\" element to a true value.\n\nremovetree( $dir1, $dir2, ....,\n{\nsafe => 1,\n... # other key-value pairs\n},\n);\n\nThe function returns the number of files successfully deleted.\n\nThe following keys are recognised in the option hash:\n\nverbose => $bool\nIf present, will cause \"removetree\" to print the name of each file as it is unlinked.\nBy default nothing is printed.\n\nsafe => $bool\nWhen set to a true value, will cause \"removetree\" to skip the files for which the\nprocess lacks the required privileges needed to delete files, such as delete privileges\non VMS. In other words, the code will make no attempt to alter file permissions. Thus,\nif the process is interrupted, no filesystem object will be left in a more permissive\nmode.\n\nkeeproot => $bool\nWhen set to a true value, will cause all files and subdirectories to be removed, except\nthe initially specified directories. This comes in handy when cleaning out an\napplication's scratch directory.\n\nremovetree( '/tmp', {keeproot => 1} );\n\nresult => \\$res\nIf present, it should be a reference to a scalar. This scalar will be made to reference\nan array, which will be used to store all files and directories unlinked during the\ncall. If nothing is unlinked, the array will be empty.\n\nremovetree( '/tmp', {result => \\my $list} );\nprint \"unlinked $\\n\" for @$list;\n\nThis is a useful alternative to the \"verbose\" key.\n\nerror => \\$err\nIf present, it should be a reference to a scalar. This scalar will be made to reference\nan array, which will be used to store any errors that are encountered. See the \"ERROR\nHANDLING\" section for more information.\n\nRemoving things is a much more dangerous proposition than creating things. As such,\nthere are certain conditions that \"removetree\" may encounter that are so dangerous that\nthe only sane action left is to kill the program.\n\nUse \"error\" to trap all that is reasonable (problems with permissions and the like), and\nlet it die if things get out of hand. This is the safest course of action.\n" }, { "name": "rmtree", "content": "" }, { "name": "rmtree", "content": "" }, { "name": "rmtree", "content": "" }, { "name": "rmtree", "content": "The \"rmtree()\" function provide the legacy interface of \"removetree()\" with a different\ninterpretation of the arguments passed. The behaviour and return value of the function is\notherwise identical to \"removetree()\".\n\nNOTE: For security reasons, we strongly advise use of the hashref-as-final-argument syntax,\nspecifically with a setting of the \"safe\" element to a true value.\n\nrmtree( $dir1, $dir2, ....,\n{\nsafe => 1,\n... # other key-value pairs\n},\n);\n\nERROR HANDLING\nNOTE:\nThe following error handling mechanism is consistent throughout all code paths EXCEPT in\ncases where the ROOT node is nonexistent. In version 2.11 the maintainers attempted to\nrectify this inconsistency but too many downstream modules encountered problems. In such\ncase, if you require root node evaluation or error checking prior to calling \"makepath\" or\n\"removetree\", you should take additional precautions.\n\nIf \"makepath\" or \"removetree\" encounters an error, a diagnostic message will be printed to\n\"STDERR\" via \"carp\" (for non-fatal errors) or via \"croak\" (for fatal errors).\n\nIf this behaviour is not desirable, the \"error\" attribute may be used to hold a reference to a\nvariable, which will be used to store the diagnostics. The variable is made a reference to an\narray of hash references. Each hash contain a single key/value pair where the key is the name of\nthe file, and the value is the error message (including the contents of $! when appropriate). If\na general error is encountered the diagnostic key will be empty.\n\nAn example usage looks like:\n\nremovetree( 'foo/bar', 'bar/rat', {error => \\my $err} );\nif ($err && @$err) {\nfor my $diag (@$err) {\nmy ($file, $message) = %$diag;\nif ($file eq '') {\nprint \"general error: $message\\n\";\n}\nelse {\nprint \"problem unlinking $file: $message\\n\";\n}\n}\n}\nelse {\nprint \"No error encountered\\n\";\n}\n\nNote that if no errors are encountered, $err will reference an empty array. This means that $err\nwill always end up TRUE; so you need to test @$err to determine if errors occurred.\n\nNOTES\n\"File::Path\" blindly exports \"mkpath\" and \"rmtree\" into the current namespace. These days, this\nis considered bad style, but to change it now would break too much code. Nonetheless, you are\ninvited to specify what it is you are expecting to use:\n\nuse File::Path 'rmtree';\n\nThe routines \"makepath\" and \"removetree\" are not exported by default. You must specify which\nones you want to use.\n\nuse File::Path 'removetree';\n\nNote that a side-effect of the above is that \"mkpath\" and \"rmtree\" are no longer exported at\nall. This is due to the way the \"Exporter\" module works. If you are migrating a codebase to use\nthe new interface, you will have to list everything explicitly. But that's just good practice\nanyway.\n\nuse File::Path qw(removetree rmtree);\n\nAPI CHANGES\nThe API was changed in the 2.0 branch. For a time, \"mkpath\" and \"rmtree\" tried, unsuccessfully,\nto deal with the two different calling mechanisms. This approach was considered a failure.\n\nThe new semantics are now only available with \"makepath\" and \"removetree\". The old semantics\nare only available through \"mkpath\" and \"rmtree\". Users are strongly encouraged to upgrade to at\nleast 2.08 in order to avoid surprises.\n\nSECURITY CONSIDERATIONS\nThere were race conditions in the 1.x implementations of File::Path's \"rmtree\" function\n(although sometimes patched depending on the OS distribution or platform). The 2.0 version\ncontains code to avoid the problem mentioned in CVE-2002-0435.\n\nSee the following pages for more information:\n\nhttp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=286905\nhttp://www.nntp.perl.org/group/perl.perl5.porters/2005/01/msg97623.html\nhttp://www.debian.org/security/2005/dsa-696\n\nAdditionally, unless the \"safe\" parameter is set (or the third parameter in the traditional\ninterface is TRUE), should a \"removetree\" be interrupted, files that were originally in\nread-only mode may now have their permissions set to a read-write (or \"delete OK\") mode.\n\nThe following CVE reports were previously filed against File-Path and are believed to have been\naddressed:\n\n* \n\n* \n\nIn February 2017 the cPanel Security Team reported an additional vulnerability in File-Path. The\n\"chmod()\" logic to make directories traversable can be abused to set the mode on an\nattacker-chosen file to an attacker-chosen value. This is due to the\ntime-of-check-to-time-of-use (TOCTTOU) race condition\n() between the \"stat()\" that decides\nthe inode is a directory and the \"chmod()\" that tries to make it user-rwx. CPAN versions 2.13\nand later incorporate a patch provided by John Lightsey to address this problem. This\nvulnerability has been reported as CVE-2017-6512.\n" } ] }, "DIAGNOSTICS": { "content": "FATAL errors will cause the program to halt (\"croak\"), since the problem is so severe that it\nwould be dangerous to continue. (This can always be trapped with \"eval\", but it's not a good\nidea. Under the circumstances, dying is the best thing to do).\n\nSEVERE errors may be trapped using the modern interface. If the they are not trapped, or if the\nold interface is used, such an error will cause the program will halt.\n\nAll other errors may be trapped using the modern interface, otherwise they will be \"carp\"ed\nabout. Program execution will not be halted.\n\nmkdir [path]: [errmsg] (SEVERE)\n\"makepath\" was unable to create the path. Probably some sort of permissions error at the\npoint of departure or insufficient resources (such as free inodes on Unix).\n\nNo root path(s) specified\n\"makepath\" was not given any paths to create. This message is only emitted if the routine\nis called with the traditional interface. The modern interface will remain silent if given\nnothing to do.\n\nNo such file or directory\nOn Windows, if \"makepath\" gives you this warning, it may mean that you have exceeded your\nfilesystem's maximum path length.\n\ncannot fetch initial working directory: [errmsg]\n\"removetree\" attempted to determine the initial directory by calling \"Cwd::getcwd\", but the\ncall failed for some reason. No attempt will be made to delete anything.\n\ncannot stat initial working directory: [errmsg]\n\"removetree\" attempted to stat the initial directory (after having successfully obtained\nits name via \"getcwd\"), however, the call failed for some reason. No attempt will be made to\ndelete anything.\n\ncannot chdir to [dir]: [errmsg]\n\"removetree\" attempted to set the working directory in order to begin deleting the objects\ntherein, but was unsuccessful. This is usually a permissions issue. The routine will\ncontinue to delete other things, but this directory will be left intact.\n\ndirectory [dir] changed before chdir, expected dev=[n] ino=[n], actual dev=[n] ino=[n],\naborting. (FATAL)\n\"removetree\" recorded the device and inode of a directory, and then moved into it. It then\nperformed a \"stat\" on the current directory and detected that the device and inode were no\nlonger the same. As this is at the heart of the race condition problem, the program will die\nat this point.\n\ncannot make directory [dir] read+writeable: [errmsg]\n\"removetree\" attempted to change the permissions on the current directory to ensure that\nsubsequent unlinkings would not run into problems, but was unable to do so. The permissions\nremain as they were, and the program will carry on, doing the best it can.\n\ncannot read [dir]: [errmsg]\n\"removetree\" tried to read the contents of the directory in order to acquire the names of\nthe directory entries to be unlinked, but was unsuccessful. This is usually a permissions\nissue. The program will continue, but the files in this directory will remain after the\ncall.\n\ncannot reset chmod [dir]: [errmsg]\n\"removetree\", after having deleted everything in a directory, attempted to restore its\npermissions to the original state but failed. The directory may wind up being left behind.\n\ncannot remove [dir] when cwd is [dir]\nThe current working directory of the program is /some/path/to/here and you are attempting to\nremove an ancestor, such as /some/path. The directory tree is left untouched.\n\nThe solution is to \"chdir\" out of the child directory to a place outside the directory tree\nto be removed.\n\ncannot chdir to [parent-dir] from [child-dir]: [errmsg], aborting. (FATAL)\n\"removetree\", after having deleted everything and restored the permissions of a directory,\nwas unable to chdir back to the parent. The program halts to avoid a race condition from\noccurring.\n\ncannot stat prior working directory [dir]: [errmsg], aborting. (FATAL)\n\"removetree\" was unable to stat the parent directory after having returned from the child.\nSince there is no way of knowing if we returned to where we think we should be (by comparing\ndevice and inode) the only way out is to \"croak\".\n\nprevious directory [parent-dir] changed before entering [child-dir], expected dev=[n] ino=[n],\nactual dev=[n] ino=[n], aborting. (FATAL)\nWhen \"removetree\" returned from deleting files in a child directory, a check revealed that\nthe parent directory it returned to wasn't the one it started out from. This is considered a\nsign of malicious activity.\n\ncannot make directory [dir] writeable: [errmsg]\nJust before removing a directory (after having successfully removed everything it\ncontained), \"removetree\" attempted to set the permissions on the directory to ensure it\ncould be removed and failed. Program execution continues, but the directory may possibly not\nbe deleted.\n\ncannot remove directory [dir]: [errmsg]\n\"removetree\" attempted to remove a directory, but failed. This may be because some objects\nthat were unable to be removed remain in the directory, or it could be a permissions issue.\nThe directory will be left behind.\n\ncannot restore permissions of [dir] to [0nnn]: [errmsg]\nAfter having failed to remove a directory, \"removetree\" was unable to restore its\npermissions from a permissive state back to a possibly more restrictive setting.\n(Permissions given in octal).\n\ncannot make file [file] writeable: [errmsg]\n\"removetree\" attempted to force the permissions of a file to ensure it could be deleted,\nbut failed to do so. It will, however, still attempt to unlink the file.\n\ncannot unlink file [file]: [errmsg]\n\"removetree\" failed to remove a file. Probably a permissions issue.\n\ncannot restore permissions of [file] to [0nnn]: [errmsg]\nAfter having failed to remove a file, \"removetree\" was also unable to restore the\npermissions on the file to a possibly less permissive setting. (Permissions given in octal).\n\nunable to map [owner] to a uid, ownership not changed\");\n\"makepath\" was instructed to give the ownership of created directories to the symbolic name\n[owner], but \"getpwnam\" did not return the corresponding numeric uid. The directory will be\ncreated, but ownership will not be changed.\n\nunable to map [group] to a gid, group ownership not changed\n\"makepath\" was instructed to give the group ownership of created directories to the\nsymbolic name [group], but \"getgrnam\" did not return the corresponding numeric gid. The\ndirectory will be created, but group ownership will not be changed.\n", "subsections": [] }, "SEE ALSO": { "content": "* File::Remove\n\nAllows files and directories to be moved to the Trashcan/Recycle Bin (where they may later\nbe restored if necessary) if the operating system supports such functionality. This feature\nmay one day be made available directly in \"File::Path\".\n\n* File::Find::Rule\n\nWhen removing directory trees, if you want to examine each file to decide whether to delete\nit (and possibly leaving large swathes alone), File::Find::Rule offers a convenient and\nflexible approach to examining directory trees.\n", "subsections": [] }, "BUGS AND LIMITATIONS": { "content": "The following describes File::Path limitations and how to report bugs.\n\nMULTITHREADED APPLICATIONS\nFile::Path \"rmtree\" and \"removetree\" will not work with multithreaded applications due to its\nuse of \"chdir\". At this time, no warning or error is generated in this situation. You will\ncertainly encounter unexpected results.\n\nThe implementation that surfaces this limitation will not be changed. See the File::Path::Tiny\nmodule for functionality similar to File::Path but which does not \"chdir\".\n\nNFS Mount Points\nFile::Path is not responsible for triggering the automounts, mirror mounts, and the contents of\nnetwork mounted filesystems. If your NFS implementation requires an action to be performed on\nthe filesystem in order for File::Path to perform operations, it is strongly suggested you\nassure filesystem availability by reading the root of the mounted filesystem.\n\nREPORTING BUGS\nPlease report all bugs on the RT queue, either via the web interface:\n\n\n\nor by email:\n\nbug-File-Path@rt.cpan.org\n\nIn either case, please attach patches to the bug report rather than including them inline in the\nweb post or the body of the email.\n\nYou can also send pull requests to the Github repository:\n\n\n", "subsections": [] }, "ACKNOWLEDGEMENTS": { "content": "Paul Szabo identified the race condition originally, and Brendan O'Dea wrote an implementation\nfor Debian that addressed the problem. That code was used as a basis for the current code. Their\nefforts are greatly appreciated.\n\nGisle Aas made a number of improvements to the documentation for 2.07 and his advice and\nassistance is also greatly appreciated.\n", "subsections": [] }, "AUTHORS": { "content": "Prior authors and maintainers: Tim Bunce, Charles Bailey, and David Landgren\n.\n\nCurrent maintainers are Richard Elberger and James (Jim) Keenan\n.\n", "subsections": [] }, "CONTRIBUTORS": { "content": "Contributors to File::Path, in alphabetical order by first name.\n\n\nCharlie Gonzalez \nCraig A. Berry \nJames E Keenan \nJohn Lightsey \nNigel Horne \nRichard Elberger \nRyan Yee \nSkye Shaw \nTom Lutz \nWill Sheppard \n", "subsections": [] }, "COPYRIGHT": { "content": "This module is copyright (C) Charles Bailey, Tim Bunce, David Landgren, James Keenan and Richard\nElberger 1995-2020. All rights reserved.\n", "subsections": [] }, "LICENSE": { "content": "This library is free software; you can redistribute it and/or modify it under the same terms as\nPerl itself.\n", "subsections": [] } } } }