unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: Ricardo Wurmus <rekado@elephly.net>, 43443@debbugs.gnu.org
Subject: [bug#43443] [PATCH] gnu: Add python-pypandoc.
Date: Wed, 16 Sep 2020 16:57:47 +0200	[thread overview]
Message-ID: <m17dstzs44.fsf@khs-macbook.home> (raw)
In-Reply-To: <878sdavxrp.fsf@elephly.net>

Hi Ricardo,

Thanks for your comments!

> Should this really be the Haskell library variants?  Or just the
> executables?  If it’s just the executables you can use the “pandoc” and
> “pandoc-citeproc” packages.

Ooops, I didn't know there were distinct packages for that! The binaries
are sufficient here.

> It would be better to avoid this huge monolithic package.  Does
> texlive-tiny work?  If it doesn’t: what else does it need that could be
> added to a texlive-union?

texlive-tiny doesn't work, and after experimenting for about an hour
I have given up on finding a small combination of packages for
a texlive-union. It needs ifluatex.sty which apparently is part of
texlive-latex-oberdiek, but if I add that package the test fails
in creating a temporary directory for whatever reason.

Another shortcut is disabling the one test case that depends
on LaTeX, and thus completely remove texlive from native-inputs.
Does that sound like an acceptable solution?

Cheers,
  Konrad




  reply	other threads:[~2020-09-16 15:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16  9:59 [bug#43443] [PATCH] gnu: Add python-pypandoc Konrad Hinsen
2020-09-16 10:09 ` Ricardo Wurmus
2020-09-16 14:57   ` Konrad Hinsen [this message]
2020-09-16 15:18     ` Ricardo Wurmus
2020-09-16 16:36       ` Konrad Hinsen
2020-09-16 16:37       ` Konrad Hinsen
2020-09-16 19:31         ` Ricardo Wurmus
2020-09-17  5:54           ` Konrad Hinsen
2020-09-17  9:43             ` bug#43443: " Ricardo Wurmus
2020-09-17  7:24         ` [bug#43443] " Konrad Hinsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m17dstzs44.fsf@khs-macbook.home \
    --to=konrad.hinsen@fastmail.net \
    --cc=43443@debbugs.gnu.org \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).