~/f/cabal-install/RPMS.2017 ~/f/cabal-install ~/f/cabal-install RPMS.2017/cabal-install-3.2.0.0-0.0.x86_64.rpm RPMS/cabal-install-3.2.0.0-0.0.x86_64.rpm differ: byte 225, line 1 Comparing cabal-install-3.2.0.0-0.0.x86_64.rpm to cabal-install-3.2.0.0-0.0.x86_64.rpm comparing the rpm tags of cabal-install --- old-rpm-tags +++ new-rpm-tags @@ -116,7 +116,7 @@ /usr/share/doc/packages/cabal-install/changelog cd4a819d5f4f4e9345a5a94985aefdd9e6b9cec59dd9459410338e391479934a 2 /usr/share/licenses/cabal-install 0 /usr/share/licenses/cabal-install/LICENSE 2c1b34deedc2b2e4c0ecae58741c379054e6e983efaf81712639cef45d768151 128 -/usr/share/man/man1/cabal.1.gz 6ddede8347d1cb8017ec52d44656aa0f044b3c45531b17696c6c031951d6d21f 2 +/usr/share/man/man1/cabal.1.gz e46eff3f2d3a780677119efa124ebed1d99d00e5821a22d9b9431dd9d62d3757 2 ___QF_CHECKSUM___ comparing rpmtags comparing RELEASE comparing PROVIDES comparing scripts comparing filelist comparing file checksum creating rename script RPM file checksum differs. Extracting packages /usr/share/man/man1/cabal.1 differs (troff or preprocessor input, ASCII text, with very long lines) --- old//usr/share/man/man1/cabal.1 2021-09-19 07:58:12.367088176 +0000 +++ new//usr/share/man/man1/cabal.1 2021-09-19 07:58:12.639090113 +0000 @@ -47936,3 +47936,1142 @@ Run haddock for Executables targets .RE +\-\-tests +.br +.RS +Run haddock for Test Suite targets +.RE + +\-\-benchmarks +.br +.RS +Run haddock for Benchmark targets +.RE + +\-\-foreign-libraries +.br +.RS +Run haddock for Foreign Library targets +.RE + +\-\-all +.br +.RS +Run haddock for all targets +.RE + +\-\-internal +.br +.RS +Run haddock for internal modules and include all symbols +.RE + +\-\-css +.I PATH +.RS +Use PATH as the haddock stylesheet +.RE + +\-\-hyperlink-source, \-\-hyperlink-sources, \-\-hyperlinked-source +.br +.RS +Hyperlink the documentation to the source code +.RE + +\-\-quickjump +.br +.RS +Generate an index for interactive documentation navigation +.RE + +\-\-hscolour-css +.I PATH +.RS +Use PATH as the HsColour stylesheet +.RE + +\-\-contents-location +.I URL +.RS +Bake URL in as the location for the contents page +.RE + +\-\-with-ghc +.I PATH +.RS +give the path to ghc +.RE + +\-\-with-haddock +.I PATH +.RS +give the path to haddock +.RE + +\-\-ghc-option +.I OPT +.RS +give an extra option to ghc (no need to quote options containing spaces) +.RE + +\-\-haddock-option +.I OPT +.RS +give an extra option to haddock (no need to quote options containing spaces) +.RE + +\-\-ghc-options +.I OPTS +.RS +give extra options to ghc +.RE + +\-\-haddock-options +.I OPTS +.RS +give extra options to haddock +.RE + +.RE + +.B cabal v1-install + +Usage: cabal v1-install [FLAGS] + or: cabal v1-install [FLAGS] PACKAGES + + +Installs one or more packages. By default, the installed package will be +registered in the user's package database or, if a sandbox is present in the +current directory, inside the sandbox. + +If PACKAGES are specified, downloads and installs those packages. Otherwise, +install the package in the current directory (and/or its dependencies) (there +must be exactly one .cabal file in the current directory). + +When using a sandbox, the flags for `v1-install` only affect the current +command and have no effect on future commands. (To achieve that, +`v1-configure` must be used.) +In contrast, without a sandbox, the flags to `v1-install` are saved and affect +future commands such as `v1-build` and `v1-repl`. See the help for +`v1-configure` for a list of commands being affected. + +Installed executables will by default (and without a sandbox) be put into +`~/.cabal/bin/`. If you want installed executable to be available globally, +make sure that the PATH environment variable contains that directory. +When using a sandbox, executables will be put into `$SANDBOX/bin/` (by +default: `./.cabal-sandbox/bin/`). + +When specifying --bindir, consider also specifying --datadir; this way the +sandbox can be deleted and the executable should continue working as long as +bindir and datadir are left untouched. + + +The flags --with-PROG and --PROG-option(s) can be used with the following programs: + alex ar c2hs cpphs doctest gcc ghc ghc-pkg ghcjs ghcjs-pkg greencard haddock + happy haskell-suite haskell-suite-pkg hmake hpc hsc2hs hscolour jhc ld + pkg-config runghc strip tar uhc + +Examples: + cabal v1-install Package in the current directory + cabal v1-install foo Package from the hackage server + cabal v1-install foo-1.0 Specific version of a package + cabal v1-install 'foo < 2' Constrained package version + cabal v1-install haddock --bindir=$HOME/hask-bin/ --datadir=$HOME/hask-data/ + Change installation destination + +The v1-install command is a part of the legacy v1 style of cabal usage. + +It is a legacy feature and will be removed in a future release of +cabal-install. Please file a bug if you cannot replicate a working v1- use +case with the nix-style commands. + +For more information, see: +https://cabal.readthedocs.io/en/latest/nix-local-build-overview.html + + +Flags: +.RS +\-v, \-\-verbose +.RI [ n ] +.RS +Control verbosity (n is 0--3, default verbosity level is 1) +.RE + +\-\-builddir, \-\-distdir, \-\-distpref +.I DIR +.RS +The directory where Cabal puts generated build files (default dist) +.RE + +\-g, \-\-ghc +.RS +compile with GHC +.RE + +\-\-ghcjs +.RS +compile with GHCJS +.RE + +\-\-uhc +.RS +compile with UHC +.RE + +\-\-haskell-suite +.RS +compile with a haskell-suite compiler +.RE + +\-\-cabal-file +.I PATH +.RS +use this Cabal file +.RE + +\-w, \-\-with-compiler overalldiffered=1 (not bit-by-bit identical) overall=1