unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: swedebugia@riseup.net, 33844@debbugs.gnu.org,
	Pierre Neidhardt <mail@ambrevar.xyz>
Subject: bug#33844: Rename ghc-pandoc to pandoc
Date: Wed, 07 Oct 2020 17:27:32 +0200	[thread overview]
Message-ID: <87o8le83a3.fsf@gmail.com> (raw)
In-Reply-To: <87y2lj53r9.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 09 Sep 2020 18:11:38 +0200")

Dear,

On Wed, 09 Sep 2020 at 18:11, Ricardo Wurmus <rekado@elephly.net> wrote:
> zimoun <zimon.toutoune@gmail.com> writes:

>>> We should also rename all uses of ghc-pandoc in the same patch.

The packages: …

>>  - rapicorn
>>  - ganeti
>>  - manuskript
>>  - emacs-org-web-tools
>>  - emacs-ox-pandoc
>>  - ruby-pandoc-ruby

… now uses ’pandoc’ instead of ’ghc-pandoc’, see:

c22c6de453 gnu: rapicorn: Use pandoc instead of ghc-pandoc.
885332832c gnu: ganeti: Use pandoc instead of ghc-pandoc.
5dc5a3116b gnu: manuskript: Use pandoc instead of ghc-pandoc.
991c61678b gnu: emacs-org-web-tools: Use pandoc instead of ghc-pandoc.
d37279ee1e gnu: emacs-ox-pandoc: Use pandoc instead of ghc-pandoc.
8cc8e584ab gnu: ruby-pandoc-ruby: Use pandoc instead of ghc-pandoc.


> If these packages only use the “pandoc” executable they should use the
> “pandoc” package instead of “ghc-pandoc”.  “ghc-pandoc” is only meant
> for Haskell packages that use Pandoc as a library.  This is a much rarer
> case, so we can assume that most packages should use “pandoc” instead of
> “ghc-pandoc”.

The only non-Haskell package remaining is ’gnu/packages/mail.scm
(muchsync)’.  Once this package is done (see #43848 [1]), we should be
able to close this bug, I guess.


[1] <http://issues.guix.gnu.org/issue/43848>

All the best,
simon




  reply	other threads:[~2020-10-07 15:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-23  8:46 bug#33844: Rename ghc-pandoc to pandoc swedebugia
2020-02-26 10:06 ` Pierre Neidhardt
     [not found] ` <878skpacih.fsf@ambrevar.xyz>
2020-02-26 10:23   ` Efraim Flashner
2020-02-26 10:23   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-02-26 11:57   ` Ricardo Wurmus
     [not found]   ` <87wo89imsx.fsf@elephly.net>
2020-02-26 12:17     ` Pierre Neidhardt
     [not found]     ` <87wo898rv3.fsf@ambrevar.xyz>
2020-02-26 12:52       ` Pierre Neidhardt
2020-09-09 16:08     ` zimoun
2020-09-09 16:11       ` Ricardo Wurmus
2020-10-07 15:27         ` zimoun [this message]
2020-12-19  0:03           ` zimoun
     [not found]   ` <20200226102314.GE12956@E5400>
2020-02-27  1:23     ` Mike Gerwitz
     [not found]     ` <87pne0q0wb.fsf@gnu.org>
2020-02-27 13:10       ` zimoun
     [not found]       ` <CAJ3okZ2-Mz=Bh6dbg7BEcH54Vc0RMRDfCOkqTJzP=cW4S2wAJg@mail.gmail.com>
2020-02-28  5:03         ` Mike Gerwitz

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=87o8le83a3.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=33844@debbugs.gnu.org \
    --cc=mail@ambrevar.xyz \
    --cc=rekado@elephly.net \
    --cc=swedebugia@riseup.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).