From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "M" <matf@disr.it>, <58387@debbugs.gnu.org>
Subject: [bug#58387] [PATCH 1/2] gnu: Add python-pylatexenc. * gnu/packages/python-xyz.scm (python-pylatexenc): New variable.
Date: Sun, 09 Oct 2022 09:34:20 +0100 [thread overview]
Message-ID: <CNH95VUUOFJ2.2H7WUE07I6T16@guix-framework> (raw)
In-Reply-To: <20221009030224.10447-1-matf@disr.it>
Hey,
On Sun Oct 9, 2022 at 4:02 AM BST, M wrote:
> + (name "python-pylatexenc")
> + (version "2.10")
> + (source (origin
> + (method url-fetch)
> + (uri (pypi-uri "pylatexenc" version))
Could you add a ``file-name'' field? Something like:
(file-name (string-append name "-" version ".tar.gz"))
> + (synopsis
> + "Simple LaTeX parser providing latex-to-unicode and unicode-to-latex conversion")
> + (description
> + "Simple LaTeX parser providing latex-to-unicode and unicode-to-latex conversion")
You'll want to shorten the synopsis and make the description a full sentence.
-- (
next prev parent reply other threads:[~2022-10-09 8:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 3:01 [bug#58387] [PATCH 0/2] Add cobib M
2022-10-09 3:02 ` [bug#58387] [PATCH 1/2] gnu: Add python-pylatexenc. * gnu/packages/python-xyz.scm (python-pylatexenc): New variable M
2022-10-09 3:02 ` [bug#58387] [PATCH 2/2] gnu: Add cobib. * gnu/packages/python-xyz.scm (python-cobib): " M
2022-10-09 8:37 ` ( via Guix-patches via
2022-10-09 8:34 ` ( via Guix-patches via [this message]
2022-10-09 11:04 ` [bug#58387] [PATCH v2 1/2] gnu: Add python-pylatexenc. * gnu/packages/python-xyz.scm (python-pylatexenc): " M
2022-10-09 11:04 ` [bug#58387] [PATCH v2 2/2] gnu: Add cobib. * gnu/packages/python-xyz.scm (python-cobib): " M
2022-10-09 11:11 ` ( via Guix-patches via
2022-10-09 11:11 ` [bug#58387] [PATCH v2 1/2] gnu: Add python-pylatexenc. * gnu/packages/python-xyz.scm (python-pylatexenc): " ( via Guix-patches via
2022-10-09 11:14 ` [bug#58387] [PATCH v3 " M
2022-10-09 11:14 ` [bug#58387] [PATCH v3 2/2] gnu: Add cobib. * gnu/packages/python-xyz.scm (python-cobib): " M
2022-10-09 11:18 ` [bug#58387] [PATCH v4 1/2] gnu: Add python-pylatexenc. * gnu/packages/python-xyz.scm (python-pylatexenc): " M
2022-10-09 11:18 ` [bug#58387] [PATCH v4 2/2] gnu: Add cobib. * gnu/packages/python-xyz.scm (python-cobib): " M
2022-10-09 11:20 ` [bug#58387] [PATCH v5 1/2] gnu: Add python-pylatexenc. * gnu/packages/python-xyz.scm (python-pylatexenc): " M
2022-10-09 11:20 ` [bug#58387] [PATCH v5 2/2] gnu: Add cobib. * gnu/packages/python-xyz.scm (python-cobib): " M
2022-10-09 11:44 ` ( via Guix-patches via
2022-10-11 11:09 ` bug#58387: " 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=CNH95VUUOFJ2.2H7WUE07I6T16@guix-framework \
--to=guix-patches@gnu.org \
--cc=58387@debbugs.gnu.org \
--cc=matf@disr.it \
--cc=paren@disroot.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).