From 3ed166c0ce12feeab0db362e594cfde89fc8137c Mon Sep 17 00:00:00 2001 From: Nicolas Goaziou Date: Tue, 29 Aug 2023 15:47:13 +0200 Subject: [PATCH] gnu: Add texlive-cybercic. * gnu/packages/tex.scm (texlive-cybercic): New variable. --- gnu/packages/tex.scm | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/gnu/packages/tex.scm b/gnu/packages/tex.scm index d7889ccec4..eb2257c34a 100644 --- a/gnu/packages/tex.scm +++ b/gnu/packages/tex.scm @@ -77782,6 +77782,31 @@ statements, destruction notices, organization logos, and security labels to it.") (license license:expat))) +(define-public texlive-cybercic + (package + (name "texlive-cybercic") + (version (number->string %texlive-revision)) + (source (texlive-origin + name version + (list "doc/latex/cybercic/" + "source/latex/cybercic/" + "tex/latex/cybercic/") + (base32 + "0nbg4pj8dkwwkjwmd8xixgz0hx1b0sf6s7j0d372dzfgr57712cq"))) + (outputs '("out" "doc")) + (build-system texlive-build-system) + (home-page "https://ctan.org/pkg/cybercic") + (synopsis "``Controls in contents'' for the @code{cyber} package") + (description + "This package is used in concert with the @code{cyber} package to make +documents with annotations of compliance with cybersecurity requirements. +When you include this package, some notations of compliance are added to +section names as seen in the table of contents of the final document. It also +makes your document more brittle in unexpected ways: for example, when you use +@code{cybercic} in the same document as @code{hyperref}, you cannot use any +formatting in your section titles. So don't use cybercic unless you need to.") + (license license:expat))) + ;;; ;;; Avoid adding new packages to the end of this file. To reduce the chances ;;; of a merge conflict, place them above by existing packages with similar