From: Steve George <steve@futurile.net>
To: 67549@debbugs.gnu.org
Cc: Steve George <steve@futurile.net>
Subject: [bug#67549] [PATCH v2 0/2] Re: Add latexml
Date: Thu, 11 Apr 2024 23:10:38 +0100 [thread overview]
Message-ID: <cover.1712871392.git.steve@futurile.net> (raw)
In-Reply-To: <20231130171829.13457-1-ngraves@ngraves.fr>
Hi Nicolas,
You sent this back in November. As I reviewed I noticed that there were a lot of propagated-inputs, so I extended your wrap phase and moved everything into inputs. Some of the magic of gexps is at the edge of my current understanding, so perhaps there's a better way to do this?
Review:
* Move PERL5LIB propagated-inputs to wrap-program
* Update to new minor version
* Change to Git / enable tests
* functionality: tested with example
* checked with guix lint
* reroll to trigger QA build
Nicolas Graves via Guix-patches via (2):
gnu: Add perl-image-size.
gnu: Add latexml.
gnu/packages/markup.scm | 117 +++++++++++++++++++++++++++++++++++++++-
gnu/packages/perl.scm | 20 +++++++
2 files changed, 136 insertions(+), 1 deletion(-)
base-commit: c1c9d6b3cdf5955f1bf5fded2a0c496ce2e631f1
--
2.41.0
next prev parent reply other threads:[~2024-04-11 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-30 17:17 [bug#67549] [PATCH 0/2] gnu: Add latexml Nicolas Graves via Guix-patches via
2023-12-02 11:08 ` [bug#67549] [PATCH 1/2] gnu: Add perl-image-size Nicolas Graves via Guix-patches via
2023-12-02 11:08 ` [bug#67549] [PATCH 2/2] gnu: Add latexml Nicolas Graves via Guix-patches via
2024-04-11 22:10 ` Steve George [this message]
2024-04-11 22:10 ` [bug#67549] [PATCH v2 1/2] gnu: Add perl-image-size Steve George
2024-04-11 22:10 ` [bug#67549] [PATCH v2 2/2] gnu: Add latexml Steve George
2024-04-16 22:03 ` bug#67549: [PATCH v2 0/2] " Christopher Baines
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=cover.1712871392.git.steve@futurile.net \
--to=steve@futurile.net \
--cc=67549@debbugs.gnu.org \
/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).