Since Texinfo 7.0 (available in unstable) it’s now possible to produce epub files from
texinfo. I’m trying to produce an epub file for the Emacs lisp intro book, but when I try to generate it I get an error
$ TEXINPUTS=".:.:" MAKEINFO="makeinfo --force --enable-encoding -I ." texi2any --epub3 emacs-lisp-intro.texi texi2any: Archive::Zip is required for EPUB file output
zip is installed on my system
$ zip --version Copyright (c) 1990-2008 Info-ZIP - Type 'zip "-L"' for software license. This is Zip 3.0 (July 5th 2008), by Info-ZIP. Currently maintained by E. Gordon. Please send bug reports to the authors using the web page at www.info-zip.org; see README for details. Latest sources and executables are at ftp://ftp.info-zip.org/pub/infozip, as of above date; see http://www.info-zip.org/ for other sites. Compiled with gcc 12.2.0 for Unix (Linux ELF) on Jul 5 2008. Zip special compilation options: USE_EF_UT_TIME (store Universal Time) SYMLINK_SUPPORT (symbolic links supported) LARGE_FILE_SUPPORT (can read and write large files on file system) ZIP64_SUPPORT (use Zip64 to store large files in archives) UNICODE_SUPPORT (store and read UTF-8 Unicode paths) STORE_UNIX_UIDs_GIDs (store UID/GID sizes/values using new extra field) UIDGID_NOT_16BIT (old Unix 16-bit UID/GID extra field not used) [encryption, version 2.91 of 05 Jan 2007] (modified for Zip 3) Encryption notice: The encryption code of this program is not copyrighted and is put in the public domain. It was originally written in Europe and, to the best of our knowledge, can be freely distributed in both source and object forms from any country, including the USA under License Exception TSU of the U.S. Export Administration Regulations (section 740.13(e)) of 6 June 2002. Zip environment options: ZIP: [none] ZIPOPT: [none]
When I asked in #firstname.lastname@example.org someone suggested that it’s probably a Perl library that’s missing.
I looked at
texinfo in the nixpkgs tree and I saw that
texinfo is a dependency for
gcc. The function doesn’t follow the usual pattern for applications, and I don’t want to muck around with low level dependencies. What should we do?