From: Gabriel Hondet <gabrielhondet@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 56356@debbugs.gnu.org
Subject: [bug#56356] [WIP PATCH] gnu: dedukti: Update to 1.7.
Date: Sun, 10 Jul 2022 11:55:18 +0200 [thread overview]
Message-ID: <YsqiBvJaDQdvnyeO@nancy.private.lsv.fr> (raw)
In-Reply-To: <20220702134201.3cf338e1@sybil.lepiller.eu>
Hi Julien and Guix,
On Sat, Jul 02, 2022 at 01:42:01PM +0200, Julien Lepiller wrote:
> Attached is a patch to update dedukti to the latest version, 1.7. The
> patch works and dedukti seems to be working, though I don't really know
> how to use it, so maybe not :)
Sorry for the late reply, and thanks a lot for the update, the patch
seems perfect.
> The issue is with its dependent emacs-dedukti-mode. It embeds a
> reference to the "dkcheck" tool that does not exist in this version of
> the package. Instead, you're supposed to call "dk check" (the --help
> still mentions dkcheck, so maybe I did something wrong in packaging?)
>
> I noticed that emacs-dedukti-mode is 5 years old and unmaintained
> upstream, while there is a dedukti-mode provided in the git repository
> of dedukti that is only 2 years old. I don't use emacs and I don't know
> how to solve this issue, so I'm not updating the package yet.
>
> I'd appreciate some help, either to find a better substitution pattern
> in the current emacs-dedukti-mode package, or to package the one
> provided by dedukti, or maybe to figure out another direction I didn't
> see :)
Indeed, the emacs-dedukti-mode is deprecated, it would be better to just
remove it from guix recipes.
Cheers,
Gabriel
next prev parent reply other threads:[~2022-07-10 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 11:42 [bug#56356] [WIP PATCH] gnu: dedukti: Update to 1.7 Julien Lepiller
2022-07-10 9:55 ` Gabriel Hondet [this message]
2022-07-17 18:30 ` Ludovic Courtès
2022-11-03 13:07 ` bug#56356: " Julien Lepiller
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=YsqiBvJaDQdvnyeO@nancy.private.lsv.fr \
--to=gabrielhondet@gmail.com \
--cc=56356@debbugs.gnu.org \
--cc=julien@lepiller.eu \
/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).