mirror of
https://git.in.rschanz.org/ryan77627/guix.git
synced 2024-11-07 15:36:20 -05:00
gnu: Fix Texinfo markup in descriptions of Haskell packages.
* gnu/packages/haskell-xyz.scm (ghc-citeproc) (ghc-hsyaml-aeson, ghc-lukko): Fix Texinfo markup in descriptions.
This commit is contained in:
parent
5b81999c89
commit
c3c502896b
1 changed files with 4 additions and 4 deletions
|
@ -15854,7 +15854,7 @@ (define-public ghc-citeproc
|
|||
(description
|
||||
"@code{ghc-citeproc} parses @acronym{Citation Style Language, CSL} style files
|
||||
and uses them to generate a list of formatted citations and bibliography
|
||||
entries. For more information about CSL, see @urefhttps://citationstyles.org/}.")
|
||||
entries. For more information about CSL, see @uref{https://citationstyles.org/}.")
|
||||
(license license:bsd-2)))
|
||||
|
||||
(define-public ghc-commonmark
|
||||
|
@ -16579,12 +16579,12 @@ (define-public ghc-hsyaml-aeson
|
|||
"The @uref{https://yaml.org/spec/1.2/spec.html, YAML 1.2} format provides
|
||||
a much richer data-model and feature-set than the
|
||||
@uref{https://tools.ietf.org/html/rfc7159, @acronym{JavaScript Object
|
||||
Notation, JSON} format. However, sometimes it's desirable to ignore the extra
|
||||
Notation, JSON}} format. However, sometimes it's desirable to ignore the extra
|
||||
capabilities and treat YAML as if it was merely a more convenient markup
|
||||
format for humans to write JSON data. To this end this module provides a
|
||||
compatibility layer atop @code{ghc-hsyaml} ,which allows decoding YAML
|
||||
documents in the more limited JSON data-model while also providing convenience
|
||||
by reusing @code{ghc-aeson}'s @code{FromJSON instances for decoding the YAML
|
||||
by reusing @code{ghc-aeson}'s @code{FromJSON} instances for decoding the YAML
|
||||
data into native Haskell data types.")
|
||||
(license license:gpl2+)))
|
||||
|
||||
|
@ -16619,7 +16619,7 @@ (define-public ghc-lukko
|
|||
are alternative file locking packages:
|
||||
|
||||
@itemize
|
||||
@item @code{GHC.IO.Handle.Lock} in @codebase >= 4.10} is good enough for most
|
||||
@item @code{GHC.IO.Handle.Lock} in @code{base >= 4.10} is good enough for most
|
||||
use cases. However, uses only @code{Handle}s so these locks cannot be used
|
||||
for intra-process locking.
|
||||
|
||||
|
|
Loading…
Reference in a new issue